Current problem reports assigned to freebsd-stable@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
HP Blade Gen 7 and 8 IO stall with ciss driver
hello Since a while we're experiencing completely I/O stalls / stopps with some HP Blade Hardware and FreeBDS 9.1. If it occurs, we have to power cycle the server to recover. The stalls occur only every few days to weeks, so it's difficult to reproduce them; we also tried to do a lot of I/O (e.g. scrubbing nonstop) but this didn't help to reproduce more often; taking load away from the productive machines helped them to reduce the frequency stalls further, but is not a solution. We figured out, that it's probably not a zfs relevated problem, because also any dd to the swap partitions stopp's. At the moment we are investigating and try different settings for the ciss driver like set to SIMPLE Mode instead of PERFORMANCE Mode and next maybe we change the heartbeat-Settings, even we DON'T see any normally mentioned error messages on the console or in the remote logs. Our main question: does anybody have similar experiences? Maybe on hp supported os? With best regards, Philipp Maechler Some more information: I/O Stall: The only solution to resolve the state is to "powercycle" the server. Any network traffic or processing stuff also like entering kernel debugger is possible, but shows only full I/O Queues... reproducing: scrubbing nonstop helps, but does result in a stall every week instead of every 4 weeks... so nothing like 'next hour'. Hardware: G7: hp blade BL465cG7: hp smart array p410i G8: hp blade BL465cG8: hp smart array P220i ciss0: port 0x4000-0x40ff mem 0xfdd0-0xfddf,0xfdcf-0xfdcf03ff irq 44 at device 0.0 on pci3 ciss0: PERFORMANT Transport On all systems, we are already on the latest bios and firmware releases on controller's (G8: Raid Controller Firmware 3.54) . FreeBSD: 9.1-RELEASE-p3 / we also tried kind of a backport of some patches to ciss from head, didn't change anything. * driver: ciss We didn't try stuff like FB 8.3 because we'd like to have userland dtrace and it's lot of work for transferring productive systems to that - maybe we will have to in future. So the only question now: Is somebody else experiencing similar issues? Maybe on hp support os? -- Hostpoint AG | The Data Residence | St. Dionysstrasse 31 | Postfach | CH-8640 Rapperswil-Jona Tel +41 844 800777 | Fax +41 844 090909 | http://www.hostpoint.ch ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD-9.1: machine reboots during snapshot creation, LORs found
On Sun, 16-Jun-2013 at 12:30:07 +0200, Jeremy Chadwick wrote: > On Sun, Jun 16, 2013 at 11:55:38AM +0200, Andre Albsmeier wrote: > > On Sun, 16-Jun-2013 at 10:49:37 +0200, Jeremy Chadwick wrote: > > > On Sun, Jun 16, 2013 at 10:02:39AM +0200, Andre Albsmeier wrote: > > > > On Sun, 16-Jun-2013 at 08:54:41 +0200, Jeremy Chadwick wrote: > > > > > On Fri, May 31, 2013 at 07:25:23PM +0200, Andre Albsmeier wrote: > > > > > > On Fri, 31-May-2013 at 16:51:03 +0200, John Baldwin wrote: > > > > > > > On Friday, May 31, 2013 8:26:11 am Andre Albsmeier wrote: > > > > > > > > Each day at 5:15 we are generating snapshots on various > > > > > > > > machines. > > > > > > > > This used to work perfectly under 7-STABLE for years but since > > > > > > > > we started to use 9.1-STABLE the machine reboots in about 10% > > > > > > > > of all cases. > > > > > > > > > > > > > > > > After rebooting we find a new snapshot file which is a bit > > > > > > > > smaller than the good ones and with different permissions > > > > > > > > It does not succeed a fsck. In this example it is the one > > > > > > > > whose name is beginning with s3: > > > > > > > > > > > > > > > > -r--r- 1 root operator snapshot 72802894528 29 May > > > > > > > > 05:15 s2-2013.05.28-03.15.04 > > > > > > > > -r 1 root operator snapshot 72802893824 29 May > > > > > > > > 05:15 s3-2013.05.29-03.15.03 > > > > > > > > -r--r- 1 root operator snapshot 72802894528 28 May > > > > > > > > 14:22 s4-2013.05.23-06.38.44 > > > > > > > > -r--r- 1 root operator snapshot 72802894528 28 May > > > > > > > > 14:22 s5-2013.05.24-03.15.03 > > > > > > > > -r--r- 1 root operator snapshot 72802894528 28 May > > > > > > > > 14:22 s6-2013.05.25-03.15.03 > > > > > > > > > > > > > > > > After enabling DIAGNOSTIC, WITNESS and INVARIANTS in the kernel > > > > > > > > I see the following LORs (mksnap_ffs starts exactly at 5:15): > > > > > > > > > > > > > > > > May 29 05:15:00 palveli kernel: lock order reversal: > > > > > > > > May 29 05:15:00 palveli kernel: 1st 0xc2371da8 ufs > > > > > > > > (ufs) @ /src/src-9/sys/kern/vfs_mount.c:1240 > > > > > > > > May 29 05:15:00 palveli kernel: 2nd 0xc2371ec4 > > > > > > > > devfs (devfs) @ /src/src-9/sys/ufs/ffs/ffs_vfsops.c:1414 > > > > > > > > May 29 05:15:04 palveli kernel: lock order reversal: > > > > > > > > May 29 05:15:04 palveli kernel: 1st 0xc228471c > > > > > > > > snaplk (snaplk) @ /src/src-9/sys/ufs/ufs/ufs_vnops.c:976 > > > > > > > > May 29 05:15:04 palveli kernel: 2nd 0xc22f25e4 ufs > > > > > > > > (ufs) @ /src/src-9/sys/ufs/ffs/ffs_snapshot.c:1626 > > > > > > > > > > > > > > > > Unfortunatley no corefiles are being generated ;-(. > > > > > > > > > > > > > > > > I have checked and even rebuilt the (UFS1) fs in question > > > > > > > > from scratch. I have also seen this happen on an UFS2 on > > > > > > > > another machine and on a third one when running "dump -L" > > > > > > > > on a root fs. > > > > > > > > > > > > > > > > Any hints of how to proceed? > > > > > > > > > > > > > > Would it be possible to setup a serial console that is logged on > > > > > > > this machine > > > > > > > to see if it is panic'ing but failing to write out a crashdump? > > > > > > > > > > > > I'll try to arrange that. It'll take a bit since this > > > > > > box is 200 km away... > > > > > > > > > > > > Maybe I'll find another one nearby to reproduce it... > > > > > > > > > > SPECIFICALLY regarding "lack of crash dumps": I need to see the > > > > > following: > > > > > > > > > > * cat /etc/rc.conf > > > > > * cat /etc/fstab > > > > > > > > > > I may need output from other commands, but shall deal with that when I > > > > > see output from the above. Thanks. > > > > > > > > No problem, see below... > > > > > > > > To make a long story short, the machine dumps core perfectly > > > > (tested that a while ago), but not when dealing with _this_ > > > > issue... > > > > > > > > I dump on da1s1b and savecore fetches it from there and puts > > > > it on /var (sitting on da0), that's faster. > > > > > > > > rc.conf (beware, rc.conf.local exists): > > > > --- > > > > rcshutdown_timeout=180 > > > > tmpmfs=YES > > > > tmpsize="$(( `/sbin/sysctl -n hw.usermem` / 300 ))m" > > > > tmpmfs_flags="$tmpmfs_flags -v 1 -n" > > > > > > > > background_fsck=NO > > > > > > > > nisdomainname=ofw.tld > > > > pflog_flags=-S > > > > > > > > syslogd_flags=-svv > > > > inetd_enable=YES > > > > inetd_flags=-l > > > > named_flags="-S 1000" > > > > named_chrootdir="" > > > > rwhod_enable=YES > > > > sshd_enable=YES > > > > amd_enable=YES > > > > amd_flags="-F /etc/amd.conf" > > > > nfs_client_enable=YES > > > > nfs_access_cache=2 > > > > mountd_flags=-n > > > > rpcbind_enable=YES > > > > > > > > ntpdate_enable=YES > > > > ntpdate_hosts=ntp > > > > ntpd_enable=YES > > > > ntpd_flags="-p /var/run/ntpd.pid" > > > > > > > > nis_client_enable=YES > > > > nis_client_flags="-s -S
Re: system sporadically hangs on shutdown after switching to WITH_NEW_XORG
On 06/16/2013 17:11, Michiel Boland wrote: Hi. Recently I switched to WITH_NEW_XORG, primarily because the stock X server with Intel driver has some issues that make it unusable for me. The new X server and Intel driver works extremely well, so kudos to whoever made this possible. Unfortunately, I am now experiencing random hangs on shutdown. On shutdown the system randomly freezes after [...] syslogd: exiting on signal 15 I would then expect to see 'Waiting (max 60 seconds) for system process 'XXX' to stop messages, but these never arrive. So it turns out that init hangs because vga_txtmouse (draw_txtmouse in fact) is hogging the clock swi. The routine is waiting for a vertical retrace which never arrives. (The new intel driver can't return to text console, so the screen just goes blank when X exits.) Some workarounds: - don't run moused (i.e. disable it in rc.conf and devd.conf) instead run the X server in combination with hald - do run moused, but then either - unplug the mouse before shutting down - build a kernel with VGA_NO_FONT_LOADING Of course the long-term fix is to remove the possibly infinite loop in draw_txtmouse. Thanks to Konstantin for his patience in helping me track this down. Cheers Michiel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD-9.1: machine reboots during snapshot creation, LORs found
On Sunday, June 16, 2013 2:39:42 am Andre Albsmeier wrote: > On Fri, 31-May-2013 at 16:51:03 +0200, John Baldwin wrote: > > On Friday, May 31, 2013 8:26:11 am Andre Albsmeier wrote: > > > Each day at 5:15 we are generating snapshots on various machines. > > > This used to work perfectly under 7-STABLE for years but since > > > we started to use 9.1-STABLE the machine reboots in about 10% > > > of all cases. > > > > > > After rebooting we find a new snapshot file which is a bit > > > smaller than the good ones and with different permissions > > > It does not succeed a fsck. In this example it is the one > > > whose name is beginning with s3: > > > > > > -r--r- 1 root operator snapshot 72802894528 29 May 05:15 > > > s2-2013.05.28-03.15.04 > > > -r 1 root operator snapshot 72802893824 29 May 05:15 > > > s3-2013.05.29-03.15.03 > > > -r--r- 1 root operator snapshot 72802894528 28 May 14:22 > > > s4-2013.05.23-06.38.44 > > > -r--r- 1 root operator snapshot 72802894528 28 May 14:22 > > > s5-2013.05.24-03.15.03 > > > -r--r- 1 root operator snapshot 72802894528 28 May 14:22 > > > s6-2013.05.25-03.15.03 > > > > > > After enabling DIAGNOSTIC, WITNESS and INVARIANTS in the kernel > > > I see the following LORs (mksnap_ffs starts exactly at 5:15): > > > > > > May 29 05:15:00 palveli kernel: lock order reversal: > > > May 29 05:15:00 palveli kernel: 1st 0xc2371da8 ufs (ufs) @ > > > /src/src-9/sys/kern/vfs_mount.c:1240 > > > May 29 05:15:00 palveli kernel: 2nd 0xc2371ec4 devfs (devfs) > > > @ /src/src-9/sys/ufs/ffs/ffs_vfsops.c:1414 > > > May 29 05:15:04 palveli kernel: lock order reversal: > > > May 29 05:15:04 palveli kernel: 1st 0xc228471c snaplk > > > (snaplk) @ /src/src-9/sys/ufs/ufs/ufs_vnops.c:976 > > > May 29 05:15:04 palveli kernel: 2nd 0xc22f25e4 ufs (ufs) @ > > > /src/src-9/sys/ufs/ffs/ffs_snapshot.c:1626 > > > > > > Unfortunatley no corefiles are being generated ;-(. > > > > > > I have checked and even rebuilt the (UFS1) fs in question > > > from scratch. I have also seen this happen on an UFS2 on > > > another machine and on a third one when running "dump -L" > > > on a root fs. > > > > > > Any hints of how to proceed? > > > > Would it be possible to setup a serial console that is logged on this > > machine > > to see if it is panic'ing but failing to write out a crashdump? > > Couldn't attach the serial console yet ;-(. But I had people > attach a KVMoverIP switch and enabled the various KDB options > in the kernel. Now we can see a bit more (see below) -- no > crashdump is being generated though. :( Unfortunately these LORs don't really help with discerning the cause of the reboot. If you have remote power access (and still wanted to test this) one option would be to change KDB to drop into the debugger on a panic. Then you could connect over the KVM and take images of the original panic along with a stack trace. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: system sporadically hangs on shutdown after switching to WITH_NEW_XORG
On Mon, Jun 17, 2013 at 09:16:56PM +0200, Michiel Boland wrote:
> On 06/16/2013 17:11, Michiel Boland wrote:
> > Hi. Recently I switched to WITH_NEW_XORG, primarily because the stock X
> > server
> > with Intel driver has some issues that make it unusable for me.
> >
> > The new X server and Intel driver works extremely well, so kudos to whoever
> > made
> > this possible.
> >
> > Unfortunately, I am now experiencing random hangs on shutdown. On shutdown
> > the
> > system randomly freezes after
> >
> > [...] syslogd: exiting on signal 15
> >
> > I would then expect to see 'Waiting (max 60 seconds) for system process
> > 'XXX' to
> > stop messages, but these never arrive.
>
> So it turns out that init hangs because vga_txtmouse (draw_txtmouse in fact)
> is
> hogging the clock swi. The routine is waiting for a vertical retrace which
> never
> arrives. (The new intel driver can't return to text console, so the screen
> just
> goes blank when X exits.)
>
> Some workarounds:
>
> - don't run moused (i.e. disable it in rc.conf and devd.conf)
>instead run the X server in combination with hald
>
> - do run moused, but then either
>
> - unplug the mouse before shutting down
>
>- build a kernel with VGA_NO_FONT_LOADING
>
> Of course the long-term fix is to remove the possibly infinite loop in
> draw_txtmouse.
>
> Thanks to Konstantin for his patience in helping me track this down.
The following patch, although a hack, should fix the issue.
Michiel tested it.
diff --git a/sys/dev/drm2/i915/intel_fb.c b/sys/dev/drm2/i915/intel_fb.c
index 3cb3b78..e41a49f 100644
--- a/sys/dev/drm2/i915/intel_fb.c
+++ b/sys/dev/drm2/i915/intel_fb.c
@@ -207,6 +207,8 @@ static void intel_fbdev_destroy(struct drm_device *dev,
}
}
+extern int sc_txtmouse_no_retrace_wait;
+
int intel_fbdev_init(struct drm_device *dev)
{
struct intel_fbdev *ifbdev;
@@ -229,6 +231,7 @@ int intel_fbdev_init(struct drm_device *dev)
drm_fb_helper_single_add_all_connectors(&ifbdev->helper);
drm_fb_helper_initial_config(&ifbdev->helper, 32);
+ sc_txtmouse_no_retrace_wait = 1;
return 0;
}
diff --git a/sys/dev/syscons/scvgarndr.c b/sys/dev/syscons/scvgarndr.c
index 6e6663c..fc7f02f 100644
--- a/sys/dev/syscons/scvgarndr.c
+++ b/sys/dev/syscons/scvgarndr.c
@@ -395,6 +395,8 @@ vga_txtblink(scr_stat *scp, int at, int flip)
{
}
+int sc_txtmouse_no_retrace_wait;
+
#ifndef SC_NO_CUTPASTE
static void
@@ -445,7 +447,9 @@ draw_txtmouse(scr_stat *scp, int x, int y)
#if 1
/* wait for vertical retrace to avoid jitter on some videocards */
crtc_addr = scp->sc->adp->va_crtc_addr;
- while (!(inb(crtc_addr + 6) & 0x08)) /* idle */ ;
+ while (!sc_txtmouse_no_retrace_wait &&
+ !(inb(crtc_addr + 6) & 0x08))
+ /* idle */ ;
#endif
c = scp->sc->mouse_char;
vidd_load_font(scp->sc->adp, 0, 32, 8, font_buf, c, 4);
pgpxVLvIhVDpR.pgp
Description: PGP signature
Re: FreeBSD-9.1: machine reboots during snapshot creation, LORs found
On Mon, 17-Jun-2013 at 21:30:31 +0200, John Baldwin wrote: > On Sunday, June 16, 2013 2:39:42 am Andre Albsmeier wrote: > > On Fri, 31-May-2013 at 16:51:03 +0200, John Baldwin wrote: > > > On Friday, May 31, 2013 8:26:11 am Andre Albsmeier wrote: > > > > Each day at 5:15 we are generating snapshots on various machines. > > > > This used to work perfectly under 7-STABLE for years but since > > > > we started to use 9.1-STABLE the machine reboots in about 10% > > > > of all cases. > > > > > > > > After rebooting we find a new snapshot file which is a bit > > > > smaller than the good ones and with different permissions > > > > It does not succeed a fsck. In this example it is the one > > > > whose name is beginning with s3: > > > > > > > > -r--r- 1 root operator snapshot 72802894528 29 May 05:15 > > > > s2-2013.05.28-03.15.04 > > > > -r 1 root operator snapshot 72802893824 29 May 05:15 > > > > s3-2013.05.29-03.15.03 > > > > -r--r- 1 root operator snapshot 72802894528 28 May 14:22 > > > > s4-2013.05.23-06.38.44 > > > > -r--r- 1 root operator snapshot 72802894528 28 May 14:22 > > > > s5-2013.05.24-03.15.03 > > > > -r--r- 1 root operator snapshot 72802894528 28 May 14:22 > > > > s6-2013.05.25-03.15.03 > > > > > > > > After enabling DIAGNOSTIC, WITNESS and INVARIANTS in the kernel > > > > I see the following LORs (mksnap_ffs starts exactly at 5:15): > > > > > > > > May 29 05:15:00 palveli kernel: lock order reversal: > > > > May 29 05:15:00 palveli kernel: 1st 0xc2371da8 ufs (ufs) @ > > > > /src/src-9/sys/kern/vfs_mount.c:1240 > > > > May 29 05:15:00 palveli kernel: 2nd 0xc2371ec4 devfs > > > > (devfs) @ /src/src-9/sys/ufs/ffs/ffs_vfsops.c:1414 > > > > May 29 05:15:04 palveli kernel: lock order reversal: > > > > May 29 05:15:04 palveli kernel: 1st 0xc228471c snaplk > > > > (snaplk) @ /src/src-9/sys/ufs/ufs/ufs_vnops.c:976 > > > > May 29 05:15:04 palveli kernel: 2nd 0xc22f25e4 ufs (ufs) @ > > > > /src/src-9/sys/ufs/ffs/ffs_snapshot.c:1626 > > > > > > > > Unfortunatley no corefiles are being generated ;-(. > > > > > > > > I have checked and even rebuilt the (UFS1) fs in question > > > > from scratch. I have also seen this happen on an UFS2 on > > > > another machine and on a third one when running "dump -L" > > > > on a root fs. > > > > > > > > Any hints of how to proceed? > > > > > > Would it be possible to setup a serial console that is logged on this > > > machine > > > to see if it is panic'ing but failing to write out a crashdump? > > > > Couldn't attach the serial console yet ;-(. But I had people > > attach a KVMoverIP switch and enabled the various KDB options > > in the kernel. Now we can see a bit more (see below) -- no > > crashdump is being generated though. > > :( Unfortunately these LORs don't really help with discerning the cause of > the reboot. If you have remote power access (and still wanted to test this) > one option would be to change KDB to drop into the debugger on a panic. > Then you could connect over the KVM and take images of the original panic > along with a stack trace. As described yesterday, I think I know why we don't get dumps: I dump on da1 and da1 is spun down. On FreeBSD-7 da1 started automatically in this case, on FreeBSD-9 it doesn't. I now dump on da0 which is running already... My suggestion is that I will try to get a dump now -- however, I have to arrange it with people using the machine. I'll come back when I have a dump ready... Thanks, -Andre > > -- > John Baldwin -- Win98: useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_9 tinderbox] failure on i386/pc98
TB --- 2013-06-18 03:05:14 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-06-18 03:05:14 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-06-18 03:05:14 - starting RELENG_9 tinderbox run for i386/pc98 TB --- 2013-06-18 03:05:14 - cleaning the object tree TB --- 2013-06-18 03:05:14 - /usr/local/bin/svn stat /src TB --- 2013-06-18 03:05:19 - At svn revision 251887 TB --- 2013-06-18 03:05:20 - building world TB --- 2013-06-18 03:05:20 - CROSS_BUILD_TESTING=YES TB --- 2013-06-18 03:05:20 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-18 03:05:20 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-18 03:05:20 - SRCCONF=/dev/null TB --- 2013-06-18 03:05:20 - TARGET=pc98 TB --- 2013-06-18 03:05:20 - TARGET_ARCH=i386 TB --- 2013-06-18 03:05:20 - TZ=UTC TB --- 2013-06-18 03:05:20 - __MAKE_CONF=/dev/null TB --- 2013-06-18 03:05:20 - cd /src TB --- 2013-06-18 03:05:20 - /usr/bin/make -B buildworld >>> World build started on Tue Jun 18 03:05:21 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Jun 18 06:00:06 UTC 2013 TB --- 2013-06-18 06:00:06 - generating LINT kernel config TB --- 2013-06-18 06:00:06 - cd /src/sys/pc98/conf TB --- 2013-06-18 06:00:06 - /usr/bin/make -B LINT TB --- 2013-06-18 06:00:06 - cd /src/sys/pc98/conf TB --- 2013-06-18 06:00:06 - /usr/sbin/config -m LINT TB --- 2013-06-18 06:00:06 - building LINT kernel TB --- 2013-06-18 06:00:06 - CROSS_BUILD_TESTING=YES TB --- 2013-06-18 06:00:06 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-18 06:00:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-18 06:00:06 - SRCCONF=/dev/null TB --- 2013-06-18 06:00:06 - TARGET=pc98 TB --- 2013-06-18 06:00:06 - TARGET_ARCH=i386 TB --- 2013-06-18 06:00:06 - TZ=UTC TB --- 2013-06-18 06:00:06 - __MAKE_CONF=/dev/null TB --- 2013-06-18 06:00:06 - cd /src TB --- 2013-06-18 06:00:06 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jun 18 06:00:06 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ale/if_ale.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/amd/amd.c /src/sys/dev/amd/amd.c: In function 'amd_action': /src/sys/dev/amd/amd.c:431: error: 'CAM_SCATTER_VALID' undeclared (first use in this function) /src/sys/dev/amd/amd.c:431: error: (Each undeclared identifier is reported only once /src/sys/dev/amd/amd.c:431: error: for each function it appears in.) /src/sys/dev/amd/amd.c:436: error: 'CAM_DATA_PHYS' undeclared (first use in this function) /src/sys/dev/amd/amd.c:473: error: 'CAM_SG_LIST_PHYS' undeclared (first use in this function) *** Error code 1 Stop in /obj/pc98.i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-06-18 06:06:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-18 06:06:16 - ERROR: failed to build LINT kernel TB --- 2013-06-18 06:06:16 - 8300.59 user 919.64 system 10861.96 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-i386-pc98.full _
[releng_9 tinderbox] failure on i386/i386
TB --- 2013-06-18 03:05:14 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-06-18 03:05:14 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-06-18 03:05:14 - starting RELENG_9 tinderbox run for i386/i386 TB --- 2013-06-18 03:05:14 - cleaning the object tree TB --- 2013-06-18 03:05:14 - /usr/local/bin/svn stat /src TB --- 2013-06-18 03:05:19 - At svn revision 251887 TB --- 2013-06-18 03:05:20 - building world TB --- 2013-06-18 03:05:20 - CROSS_BUILD_TESTING=YES TB --- 2013-06-18 03:05:20 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-18 03:05:20 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-18 03:05:20 - SRCCONF=/dev/null TB --- 2013-06-18 03:05:20 - TARGET=i386 TB --- 2013-06-18 03:05:20 - TARGET_ARCH=i386 TB --- 2013-06-18 03:05:20 - TZ=UTC TB --- 2013-06-18 03:05:20 - __MAKE_CONF=/dev/null TB --- 2013-06-18 03:05:20 - cd /src TB --- 2013-06-18 03:05:20 - /usr/bin/make -B buildworld >>> World build started on Tue Jun 18 03:05:21 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Jun 18 06:00:06 UTC 2013 TB --- 2013-06-18 06:00:06 - generating LINT kernel config TB --- 2013-06-18 06:00:06 - cd /src/sys/i386/conf TB --- 2013-06-18 06:00:06 - /usr/bin/make -B LINT TB --- 2013-06-18 06:00:06 - cd /src/sys/i386/conf TB --- 2013-06-18 06:00:06 - /usr/sbin/config -m LINT TB --- 2013-06-18 06:00:06 - building LINT kernel TB --- 2013-06-18 06:00:06 - CROSS_BUILD_TESTING=YES TB --- 2013-06-18 06:00:06 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-18 06:00:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-18 06:00:06 - SRCCONF=/dev/null TB --- 2013-06-18 06:00:06 - TARGET=i386 TB --- 2013-06-18 06:00:06 - TARGET_ARCH=i386 TB --- 2013-06-18 06:00:06 - TZ=UTC TB --- 2013-06-18 06:00:06 - __MAKE_CONF=/dev/null TB --- 2013-06-18 06:00:06 - cd /src TB --- 2013-06-18 06:00:06 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jun 18 06:00:06 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ale/if_ale.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/amd/amd.c /src/sys/dev/amd/amd.c: In function 'amd_action': /src/sys/dev/amd/amd.c:431: error: 'CAM_SCATTER_VALID' undeclared (first use in this function) /src/sys/dev/amd/amd.c:431: error: (Each undeclared identifier is reported only once /src/sys/dev/amd/amd.c:431: error: for each function it appears in.) /src/sys/dev/amd/amd.c:436: error: 'CAM_DATA_PHYS' undeclared (first use in this function) /src/sys/dev/amd/amd.c:473: error: 'CAM_SG_LIST_PHYS' undeclared (first use in this function) *** Error code 1 Stop in /obj/i386.i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-06-18 06:07:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-18 06:07:07 - ERROR: failed to build LINT kernel TB --- 2013-06-18 06:07:07 - 8392.74 user 916.47 system 10912.68 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-i386-i386.full _
[releng_9 tinderbox] failure on amd64/amd64
TB --- 2013-06-18 03:05:14 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-06-18 03:05:14 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-06-18 03:05:14 - starting RELENG_9 tinderbox run for amd64/amd64 TB --- 2013-06-18 03:05:14 - cleaning the object tree TB --- 2013-06-18 03:05:14 - /usr/local/bin/svn stat /src TB --- 2013-06-18 03:05:19 - At svn revision 251887 TB --- 2013-06-18 03:05:20 - building world TB --- 2013-06-18 03:05:20 - CROSS_BUILD_TESTING=YES TB --- 2013-06-18 03:05:20 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-18 03:05:20 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-18 03:05:20 - SRCCONF=/dev/null TB --- 2013-06-18 03:05:20 - TARGET=amd64 TB --- 2013-06-18 03:05:20 - TARGET_ARCH=amd64 TB --- 2013-06-18 03:05:20 - TZ=UTC TB --- 2013-06-18 03:05:20 - __MAKE_CONF=/dev/null TB --- 2013-06-18 03:05:20 - cd /src TB --- 2013-06-18 03:05:20 - /usr/bin/make -B buildworld >>> World build started on Tue Jun 18 03:05:21 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Tue Jun 18 06:37:35 UTC 2013 TB --- 2013-06-18 06:37:35 - generating LINT kernel config TB --- 2013-06-18 06:37:35 - cd /src/sys/amd64/conf TB --- 2013-06-18 06:37:35 - /usr/bin/make -B LINT TB --- 2013-06-18 06:37:35 - cd /src/sys/amd64/conf TB --- 2013-06-18 06:37:35 - /usr/sbin/config -m LINT TB --- 2013-06-18 06:37:35 - building LINT kernel TB --- 2013-06-18 06:37:35 - CROSS_BUILD_TESTING=YES TB --- 2013-06-18 06:37:35 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-18 06:37:35 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-18 06:37:35 - SRCCONF=/dev/null TB --- 2013-06-18 06:37:35 - TARGET=amd64 TB --- 2013-06-18 06:37:35 - TARGET_ARCH=amd64 TB --- 2013-06-18 06:37:35 - TZ=UTC TB --- 2013-06-18 06:37:35 - __MAKE_CONF=/dev/null TB --- 2013-06-18 06:37:35 - cd /src TB --- 2013-06-18 06:37:35 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jun 18 06:37:35 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ale/if_ale.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/amd/amd.c /src/sys/dev/amd/amd.c: In function 'amd_action': /src/sys/dev/amd/amd.c:431: error: 'CAM_SCATTER_VALID' undeclared (first use in this function) /src/sys/dev/amd/amd.c:431: error: (Each undeclared identifier is reported only once /src/sys/dev/amd/amd.c:431: error: for each function it appears in.) /src/sys/dev/amd/amd.c:436: error: 'CAM_DATA_PHYS' undeclared (first use in this function) /src/sys/dev/amd/amd.c:473: error: 'CAM_SG_LIST_PHYS' undeclared (first use in this function) *** Error code 1 Stop in /obj/amd64.amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-06-18 06:45:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-18 06:45:07 - ERROR: failed to build LINT ke
