Re: named.conf restored to hint zone for the root by default
I've been using a stub root zone for years without a problem. -- Christopher ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel build failure amd64
Recent cvsup with cvs up. Removed /usr/obj/.../src/sys/GENERIC. (cd /usr/src; make kernel) dies with cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/d2/FreeBSD/root/5-stable/usr/src/sys -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/dev/acpica -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/altq -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/ipfilter -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/pf -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/dev/ath -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/dev/ath/freebsd -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c: In function `probe_keyboard': /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: `KB_CONF_NO_PROBE_TEST' undeclared (first use in this function) /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: (Each undeclared identifier is reported only once /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: for each function it appears in.) *** Error code 1 The only file mentioning KB_CONF_NO_PROBE_TEST in any version appears to be src/sys/dev/kbd/atkbd.c, with no definition anywhere. -- Christopher Vance ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel build failure amd64
On Thu, Jan 13, 2005 at 11:51:24AM +1100, I wrote: Recent cvsup with cvs up. Removed /usr/obj/.../src/sys/GENERIC. (cd /usr/src; make kernel) dies with /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: `KB_CONF_NO_PROBE_TEST' undeclared (first use in this function) /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: (Each undeclared identifier is reported only once /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: for each function it appears in.) *** Error code 1 The only file mentioning KB_CONF_NO_PROBE_TEST in any version appears to be src/sys/dev/kbd/atkbd.c, with no definition anywhere. cvs repo was broken, so cvsup not working right, or something similar sorry to bother you -- Christopher Vance ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel build failure amd64
On Wed, Jan 12, 2005 at 05:19:14PM -0800, Ade Lovett wrote: Your src/ tree is not up to date, or has been otherwise mangled. The commit that added KB_CONF_NO_PROBE_TEST touched two files: Yes. My cvs repo got mangled. Either cvsup or the (not-FreeBSD) OS it's hosted on mangled something. Unfortunately cvsup didn't seem to pick that up, so I don't know if my cvsup or the mirror it's taken off is at issue. Now I need to hunt through my repo for other truncated files. :-( -- Christopher Vance ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FAILURE - WRITE_DMA timed out
On Tue, Nov 30, 2004 at 11:52:16PM -0500, Mykel wrote: I don't have any solutions for you, but I'm curious to know what kind of drives you're using... apparently SiI 3114s aren't so good with bridged (PATA-SATA) connections, and Seagates are mostly native... My disks are both Seagate ST3200822AS/3.01. On my setup (SiI3112+Seagate), I get WRITE_DMA timeo's a few times a day. Never had panics as result of the SATA tho. Okay. I have quiet if I do nothing, and it gets chatty and then dies if I try to move 10+GB to it from another place. :-( I don't even use it very heavily, it's *just* for my .oggs. Nothing else. It sucks. We're presently looking at 3Ware and others for a heavy duty network setup we're doing... hoping we can make the SiIs work instead of dropping a few grand on 3Wares... :\ but I'm not confident the SiIs are good for anything important. The whole point of my machine is NFS and other services. I don't think I even installed X. I don't want RAID or anything extra, just disks that work. I saw that the sata_sii driver in the Linux kernel on one of my other machines said there were quirks using the 3512, but I also see that the FreeBSD driver also mentions stuff about limiting transfer size. So if that were the problem, it's claimed already solved. So I'm left with deciding what to do with this machine: change OS or pray. -- Christopher Vance ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FAILURE - WRITE_DMA timed out
When I use SATA disks heavily on a 5.3-R machine (Athlon) with the SiI3512 disk controller, I get frequent (sometimes one every 1-5 minutes) WRITE_DMA timed out messages (with different blocks and both disks). It also panics with more than one kind of panic, and sometimes doesn't even get to finish the background fsck from the previous panic before dying again. Given that both disks get the WRITE_DMA messages, and the one with the OS on didn't have any problems when used with a VIA controller in a different machine, I tend to think it's either the controller or the software driving it. Would I have any joy upgrading along 5-STABLE, perhaps after I move the disk back to the machine that works, or won't that make any difference? (As in, are there any relevant ata changes since then?) I've already tried setting both hw.ata.ata_dma and hw.ata.wc to 0, but I still get these timeouts. -- Frustrated in Sydney ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP!!! USB MFC committed..
On Sun, Feb 29, 2004 at 05:01:28PM -0800, Julian Elischer wrote: The USB code in RELENG_4 has been updated to match that in -current. Please test any USB devices that are critical to you BEFORE we release 4.10 :-) gentle flame=no Would the effort to keep making 4.X releases be better spent making 5.X stable, or are the two efforts not competing for the same developer resources? /gentle -- Christopher Vance ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADSUP!!! USB MFC committed..
On Sun, Feb 29, 2004 at 11:38:04PM -0500, Richard Coleman wrote: Keeping the code bases closer together will probably make development easier, not harder. Also, this USB code will now be tested on more hardware before the release of 4.10 or 5.3. I wouldn't be surprised if someone running -stable on strange hardware finds a bug that needs fixing on both -stable and -current. Seems like a win/win to me. Okay: that leaves me a happy little vegemite. :-) [I had just been growing concerned that 5-STABLE was slipping into the next decade...] -- Christopher Vance ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
