7.0 iwi driver
i am having trouble with the speed of the iwi driver. in my ifconfig, its showing 54mbit, but its really only able to transfer a wireless B speeds (350K/s or so). i never experienced this with the iwi-firmware-kmod that was used in 6.2. is there anything i can do to resolve this and get it working at the normal G speed? thanks, -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"no matching session" in ng_pppoe.c 1.74.2.4? (RELENG_6)
Hello, Since I've updated a RELENG_6 router a few days ago, a long gone problem with ppp cropped up (again?); and I'm suspecting a regression between ng_pppoe.c 1.74.2.3 and 1.74.2.4. The problem is that the last mile carrier of the PPP provider that this router is attached to disconnects the ppp session forcibly once every 24h. Before the update, ppp would detect this and reconnect immediately. After the update, ppp doesn't recover gracefully from this anymore, but spits out on the console: ng_pppoe[5]: no matching session for hours, and tries to connect again every two minutes without success, until I manually stop and restart the userland ppp daemon (and then the connection is immediately restored with a new session). I've tried this for a few days now, and it is always the same: it's definitely not a problem on the provider's side: As soon as ppp restarts, it gets a new session without any problems and connects again. Since the last working sources were from 2007/09/25, and ng_pppoe.c was at rev. 1.74.2.3; and the new revision of ng_pppoe.c is now at 1.74.2.4; I'm suspecting that whatever was changed there could be the cause (because this "no matching session" is being logged from there). Since that router is not within easy reach, I'd rather not take the risk to compile a kernel with the old ng_pppoe.c, and have that box crash/hosed. Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 7.0-BETA4 Available
The 7.0-BETA4 builds are now available. If you would like to download an ISO image to install from they are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases//ISO-IMAGES/7.0/ If you would like to use cvsup to update an older machine the branch tag to use is still RELENG_7. For users of FreeBSD Update due to some last-minute bumps in system libraries, installed third-party applications must be recompiled as per normal for a "major" upgrade, even if upgrading from an earlier 7.0 BETA. Checksums for the ISO files are: MD5 (7.0-BETA4-amd64-bootonly.iso) = 70b53b0acd2b27c594fd0369cd5fd594 MD5 (7.0-BETA4-amd64-disc1.iso) = bfc5080c4744c4d2c907bd859fa3e14b MD5 (7.0-BETA4-amd64-disc2.iso) = a8a75cdf5afe4f960cc80744b09c096d MD5 (7.0-BETA4-amd64-docs.iso) = 63b95fc5c4156c5cecfc10fd4e0cda53 MD5 (7.0-BETA4-amd64-livefs.iso) = 4255356bb60306ffda4d20131ff76186 MD5 (7.0-BETA4-i386-bootonly.iso) = 5ed183faff01ca715a764c1a613aae13 MD5 (7.0-BETA4-i386-disc1.iso) = 4a135b4c2262aa8cfc9f07e98fa7e742 MD5 (7.0-BETA4-i386-disc2.iso) = f70d5b590c7e24ef0167f965d8d514e9 MD5 (7.0-BETA4-i386-docs.iso) = 12b04303e2e609e4b5584181505a492f MD5 (7.0-BETA4-i386-livefs.iso) = c823693011e26f03b0d799a59b669560 MD5 (7.0-BETA4-ia64-bootonly.iso) = 0a2362551732caa727cff83d01773f8f MD5 (7.0-BETA4-ia64-disc1.iso) = 1ad889292e2eca168d14f86b48b687fd MD5 (7.0-BETA4-ia64-disc2.iso) = 5ef048078a065b0b48f29e649237980b MD5 (7.0-BETA4-ia64-docs.iso) = 8e16703f49bb784ca0771b0984013854 MD5 (7.0-BETA4-ia64-livefs.iso) = d7c1eb3cb1e82af37f3ec924c9b32b75 MD5 (7.0-BETA4-pc98-bootonly.iso) = 3096e6718caeceb8077bea8d924b78f6 MD5 (7.0-BETA4-pc98-disc1.iso) = 62aa6e3c08b47b5d0ace5f95cc1c36d4 MD5 (7.0-BETA4-pc98-livefs.iso) = ffbfd22d12e599aa975d262c6ff52653 MD5 (7.0-BETA4-powerpc-bootonly.iso) = e5c336ec50a28dbd6b86ccf813e741d0 MD5 (7.0-BETA4-powerpc-disc1.iso) = 8db3620074d2de3f4f42960bf0ff760b MD5 (7.0-BETA4-powerpc-disc2.iso) = 51a205fa91d314acca2a66c628628fa9 MD5 (7.0-BETA4-powerpc-docs.iso) = d83f8e66e14298a16bd000880d1f14f6 MD5 (7.0-BETA4-sparc64-bootonly.iso) = af11f6520e7d346c48b5c561c0080346 MD5 (7.0-BETA4-sparc64-disc1.iso) = c2ba1e08bf09168ec08ca1c3621bdc18 MD5 (7.0-BETA4-sparc64-disc2.iso) = 469cfc4af15fb5ba5ba93a07e6226fb6 MD5 (7.0-BETA4-sparc64-docs.iso) = 88bc1094300ac21422434568feace660 SHA256 (7.0-BETA4-amd64-bootonly.iso) = 4329cca2614cf0c533faf462a668012f51ece8e519d561873e4a236b62b34410 SHA256 (7.0-BETA4-amd64-disc1.iso) = e8a210a17db89a76ac71aa809d8619355661206e229824d8b9258c44e8e2f7be SHA256 (7.0-BETA4-amd64-disc2.iso) = 5296c2a35c3b08077f21a24a1a5ec5b49a70bf65c6fb2d6148cdf444a1283b3b SHA256 (7.0-BETA4-amd64-docs.iso) = 202b1844314deb761d6f097ba3bb1547325290296dd6361e80d3e171fc997047 SHA256 (7.0-BETA4-amd64-livefs.iso) = 2fa79ae18182851b3346951499f8319c10bc4870bbf8c3af1e2d99b75a86d64f SHA256 (7.0-BETA4-i386-bootonly.iso) = bae7e72dffc1e80e6f88b66283dfaf2075e58de23d30fa9cd939a37bb3642464 SHA256 (7.0-BETA4-i386-disc1.iso) = 7025f7b3abee52f93fe1a369bb1ba3821987ba799cb2b05cd7303240383d7f08 SHA256 (7.0-BETA4-i386-disc2.iso) = 5e16fe392d135b3e3e02ee3b7acd391a8d1a74c14fd096f5e9dca6f5877f17a2 SHA256 (7.0-BETA4-i386-docs.iso) = fc06aca7ae4d4cc234b1800f286589a8830e24add0a8ae39ab5825caaaead23a SHA256 (7.0-BETA4-i386-livefs.iso) = e7f43cf685f4b534ce8c41b0cf61f0bc3f739ffa6537c11e199c7e46de6b3b51 SHA256 (7.0-BETA4-ia64-bootonly.iso) = 6abfb7b0111d8aced1f2178e1437cd0c8c0f60d449b05523c9d3198e0e2879b4 SHA256 (7.0-BETA4-ia64-disc1.iso) = 153f7db9d0106bf784ae537f130c77ec8f1b333ea89fe9803d6b8b343a3900b8 SHA256 (7.0-BETA4-ia64-disc2.iso) = ccdcbe99d38251245947939c8c0825fe13274296374742cb6fa4602a87ff2331 SHA256 (7.0-BETA4-ia64-docs.iso) = 2194c5e34eaf7093c811b4438efee695347cc830f89e316152fe275286bc2fbf SHA256 (7.0-BETA4-ia64-livefs.iso) = c748a4d3335c4d3a18c91185ce13242ce3055dcf6ef9604ba65387eaaba6b368 SHA256 (7.0-BETA4-pc98-bootonly.iso) = c5f3e60e9d6c67482adc6935d8c6f63f9fca5e7cb5f820991b18d4fc640a2255 SHA256 (7.0-BETA4-pc98-disc1.iso) = eb4487a56a5e58956b2951a2e56e52fadd61582ec36624983409fcde8b073298 SHA256 (7.0-BETA4-pc98-livefs.iso) = 99b44644758a97b9f88c78f51c52f358b8ac42f394ea89112358cbbfd12a21f4 SHA256 (7.0-BETA4-powerpc-bootonly.iso) = a9aa405103f74358b7fbfaa908146787190b7e71984cfd93ff47b4c3c8f92b10 SHA256 (7.0-BETA4-powerpc-disc1.iso) = eeabea5b655ae4b7308bc4248c1ca2158d3ff0f6d84dfe7fd19a3bfd197b046a SHA256 (7.0-BETA4-powerpc-disc2.iso) = a08c08c780cd54e78483a7fc96fd86ab0c85877304c4e679df85e3bd5ae4b897 SHA256 (7.0-BETA4-powerpc-docs.iso) = db986927bcd9c5ecfed40bdcc03e04e1d588202964ad66eebdeaac1757fff5ce SHA256 (7.0-BETA4-sparc64-bootonly.iso) = 7e092f1d56876c04e2cb9bd05357de1b9ebb3c5195c7563cdb6c00fcf4e26367 SHA256 (7.0-BETA4-sparc64-disc1.iso) = d442e78d356edcd342ccc0786e535e4926b8b87d084ae15206c8a479f1235f3b SHA256 (7.0-BETA4-sparc64-disc2.iso) = 6c123143919b1818a9c26caaf38dd00f759a9a8b97f235b5693a04f51a83599f SHA256 (7.0-BETA4-sparc64-docs.iso) = 8c5ad1ebeaaa23367cbbf8f2e65e526dc5756bf1528a7b0a64e6b7
Bootstrapping problem in RELENG_6
Going to yesterday's RELENG_6 userland with `buildworld` from an older RELENG_6 from July fails like this: ===> lib/libbsm (all) cc -pg -O2 -fno-strict-aliasing -pipe -march=pentium-m -I/mnt/part2/usr/src/lib\ /libbsm/../../contrib/openbsm -I/mnt/part2/usr/src/lib/libbsm/../../contrib/ope\nbsm/libbsm -c /mnt/part2/usr/src/lib/libbsm/../../contrib/openbsm/libbsm/bsm_\ io.c -o bsm_io.po /mnt/part2/usr/src/lib/libbsm/../../contrib/openbsm/libbsm/bsm_io.c: In functio\n `close_tag': /mnt/part2/usr/src/lib/libbsm/../../contrib/openbsm/libbsm/bsm_io.c:396: error:\ `AUT_ZONENAME' undeclared (first use in this function) [more of same] To fix this you need to make the new versions of the include file for /usr/include/bsm/, currently in /usr/src/sys/bsm, visible. As a workaround just copying the new files does the job. Just in case anyone else has the problem or in case anyone wants to fix this bootstrap. Martin -- %%% Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade trouble
Hi, I've got make problem, whether using portupgrade or cd /usr/ports/xx/xx && make. #uname -a FreeBSD lisa.bob.selfip.org 6.2-RELEASE-p8 FreeBSD 6.2-RELEASE-p8 #5: Sun Nov 25 18:35:33 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LISA i386 As you can see below, when it enters on configuring, it give me a prompt, I've got to quit them (they are 2, always) and it continues normally. Don't know where or what I should search for. [Updating the pkgdb in /var/db/pkg ... - 93 packages found (-0 +1) . done] ---> Upgrading 'pkg-config-0.22' to 'pkg-config-0.22_1' (devel/pkg-config) ---> Building '/usr/ports/devel/pkg-config' ===> Cleaning for pkg-config-0.22_1 ===> Vulnerability check disabled, database not found ===> Extracting for pkg-config-0.22_1 => MD5 Checksum OK for gnome2/pkg-config-0.22.tar.gz. => SHA256 Checksum OK for gnome2/pkg-config-0.22.tar.gz. ===> Patching for pkg-config-0.22_1 ===> Applying FreeBSD patches for pkg-config-0.22_1 ===> pkg-config-0.22_1 depends on executable: gmake - found ===> Configuring for pkg-config-0.22_1 ([EMAIL PROTECTED]:p3)--(/usr/ports/devel/pkg-config/work/pkg-config-0.22) #exit ([EMAIL PROTECTED]:p3)--(/usr/ports/devel/pkg-config/work/pkg-config-0.22) #exit checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether gmake sets $(MAKE)... yes [SKIP] #cat /etc/make.conf CPUTYPE?=i686 CFLAGS= -O -pipe WITHOUT_X11=yes NO_X=true NO_GAMES=true # added by use.perl 2007-11-13 20:15:49 PERL_VER=5.8.8 PERL_VERSION=5.8.8 thanks, Matthieu. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
HPET at Tyan H2000M (S3992-E) south-bridge
just some info that may save somebody else time on that. I swapped motherbards today on FreeBSD 6.2, AMD64, cvsup'd 07/18/2007 Orignal was a Tyan K8S (S2882) New is a Tyan H2000M (S3992-E) on boot, the system got stuck right before it would mount drives. A ctrl+c after waiting for a minute showed it hang somehere in /sbin/devd It continued to the login prompt, but the timer (e.g. date) never increased comparing the boot-logs showed: Timecounter "HPET" frequency 14318180 Hz quality 2000 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_hpet0: iomem 0xfed0-0xfed03fff on acpi0 Timecounter "HPET" frequency 232831 Hz quality 2000 digging thru CVSUP, I found the change in acpi_hpet.c cvsup to 6.3-PRE, make kernel, and the problem seems to be gone: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed03fff on acpi0 acpi_hpet0: HPET never increments, disabling device_attach: acpi_hpet0 attach returned 6 By accident, I found that the bios-default for HPET setable in the south-bridge of the H2000M is DISABLED. Enableing it, the logs shows: Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 looks like the simple problem in this case may have been (dam..d) bios-setting Dieter ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
AW: g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5
Just an update > > --- Scott Long <[EMAIL PROTECTED]> wrote: > > > I can geneate 30,000 I/O's per second for hours on end on several > > > types of storage hardware on FreeBSD SMP, and have no > > problems. Since > > > you're seeing this problem both when connected to a 3ware > > controller > > > and when connected to a simple ATA/SATA controller (both of > > which have > > > also been observed to do high amounts of I/O with no problems), I > > > suspect that the problem is with your disk device, not with > > FreeBSD. > > > I don't know anything about a "hyperdrive" though, so more > > information might help. > > > > > > Scott > > > > > I would say so, too... > > > > Especially because errno 5 is EIO: > > http://www.freebsd.org/cgi/man.cgi?query=errno&apropos=0&sekti > > on=0&manpath=FreeBSD+6.2-RELEASE&format=html > > > > -Arne > > I would agree with you on that, if the error (EIO) is NOT > because of the READ going wrong in the first place. > > From my understanding, the offset 81064794762854400 is NOT > within the 12 GB of the drive anymore. Or, does the offset > mean something else ? Scott, you were right in the first place, it was definitely a disk error. Thanks Dieter ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: missing .cshrc and pf.conf after upgrade to 7.0-beta3
Colin Percival wrote: Max Laier wrote: On Tuesday 04 December 2007, Colin Percival wrote: John Baldwin wrote: Considering that /etc/pf.conf is a file that users edit to configure pf(4), removing it out from under them is probably a very bad idea. The heuristics didn't work this time. :-( Yet they lose the configuration changes they might have applied to the original foo.conf. I don't think you should delete files that have changed. Maybe moving them somewhere for future reference would be the best thing to do? That is, in effect, what FreeBSD Update does -- the upgrade can always be rolled back (and /etc/pf.conf recovered) by "freebsd-update rollback". Is there any way how one can recover just pf.conf and not whole upgrade? Is there any place, where warning about this issue (removing pf.conf) should go? Because many users are using PF and if anybody from them will try your freebsd-update.sh upgrade from FreeBSD 6.2 to newer release will lose pf.conf and end up with unfirewalled machine after reboot without knowing it. (just like me) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Anyone else seeing this on a make release of 7?
> -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-freebsd- > [EMAIL PROTECTED] On Behalf Of Claus Guttesen > Sent: 05 December 2007 10:47 > To: Lawrence Farr > Cc: freebsd-stable@freebsd.org > Subject: Re: Anyone else seeing this on a make release of 7? > > > cc -Os -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > > What happens if you revert to default optimization to -O2? > > -- > regards > Claus I have no optimization settings in make.conf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: missing .cshrc and pf.conf after upgrade to 7.0-beta3
Max Laier wrote: > On Tuesday 04 December 2007, Colin Percival wrote: >> John Baldwin wrote: >>> Considering that /etc/pf.conf is a file that users edit to configure >>> pf(4), removing it out from under them is probably a very bad idea. >> >> The heuristics didn't work this time. :-( > > Yet they lose the configuration changes they might have applied to the > original foo.conf. I don't think you should delete files that have > changed. Maybe moving them somewhere for future reference would be the > best thing to do? That is, in effect, what FreeBSD Update does -- the upgrade can always be rolled back (and /etc/pf.conf recovered) by "freebsd-update rollback". Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: missing .cshrc and pf.conf after upgrade to 7.0-beta3
On Tuesday 04 December 2007, Colin Percival wrote: > John Baldwin wrote: > > On Wednesday 28 November 2007 02:47:11 pm Colin Percival wrote: > >> Miroslav Lachman wrote: > >>> I am not 100% sure, maybe I overlook something in binary major > >>> version upgrade procedure, but after upgrade from 6.2 to 7.0-BETA3 > >>> my roots ~/.cshrc was "accidentally" replaced with dist version of > >>> .cshrc and /etc/pf.conf is missing. > >> > >> The fact that /etc/pf.conf disappeared is due to it being removed > >> from the release (it is now in /usr/share/examples/etc). The fact > >> that /.cshrc was upgraded in spite of having been locally modified > >> is probably a bad idea -- I'll change the default > >> freebsd-update.conf to deal with this. > > > > Considering that /etc/pf.conf is a file that users edit to configure > > pf(4), removing it out from under them is probably a very bad idea. > > The heuristics didn't work this time. :-( > > FreeBSD Update tries to guess what users want to have done -- in this > case, the heuristic is "if a configuration file is present in release X > but not in release Y, it's probably not relevant in release Y; so let's > delete it". The case of a default configuration file being moved from > /etc/ into /usr/share/examples/etc is one which I didn't consider; but > I think the general heuristic is a good one (consider the scenario > where a /etc/foo.conf is renamed to /etc/food.conf -- with the current > heuristic, at least the user gets a warning that the file is > disappearing rather than suddenly finding that the foo daemon isn't > starting up properly for no apparent reason). Yet they lose the configuration changes they might have applied to the original foo.conf. I don't think you should delete files that have changed. Maybe moving them somewhere for future reference would be the best thing to do? -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News signature.asc Description: This is a digitally signed message part.
Re: Intel DG31PR and RTL8168/8111 issue
On Tue, Dec 04, 2007 at 07:42:34AM -0800, Abdullah Ibn Hamad Al-Marri wrote: [...] > > I'll try the patch you sent too when the server reaches the ISP and being > online. > > Do you have any comments? > The previous patch you used may have problems on multicast filtering. I'm not sure but all PCIe based controller from RealTek swapped multicast hash table register so it would be great if you can test latest patch. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone else seeing this on a make release of 7?
On 12/5/2007 12:55 PM, Lawrence Farr wrote: cc -Os -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -W return-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundan t-decls -Wno-pointer-sign -c /usr/src/bin/ed/main.c *** Error code 1 Stop in /usr/src/bin/ed. *** Error code 1 Stop in /usr/obj/usr/src/release/fixit_crunch. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. in.c:106: warning: argument 'argv' might be clobbered by 'longjmp' or 'vfork' + umount /dev Been getting it for a week or so now, it's being built on: 7.0-BETA3 FreeBSD 7.0-BETA3 #0: Mon Nov 26 01:04:55 GMT 2007 Are you sure that you are building from RELENG_7 source? It doesn't have -Werror defined, IIRC. And HEAD should be fixed by this commit: http://lists.freebsd.org/pipermail/cvs-src/2007-December/084624.html HTH, Yuri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Attention 7.x and 8.x ptmx/pts users (read if you set kern.pts.enable=1)
* Ed Schouten <[EMAIL PROTECTED]> wrote: > This also causes the dreaded `jail leak', because device nodes still > exist that have been created with make_dev_cred(), so the ucred is > still referenced. I just saw a commit flash by that disables si_cred usage in make_dev_cred(). That is indeed a good workaround for the time being. Thank you! :-) -- Ed Schouten <[EMAIL PROTECTED]> WWW: http://g-rave.nl/ pgp53MbOf2tcH.pgp Description: PGP signature
Re: Anyone else seeing this on a make release of 7?
> cc -Os -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W What happens if you revert to default optimization to -O2? -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Anyone else seeing this on a make release of 7?
> -Original Message- > From: Yuri Pankov [mailto:[EMAIL PROTECTED] > Sent: 05 December 2007 10:37 > To: Lawrence Farr > Cc: freebsd-stable@freebsd.org > Subject: Re: Anyone else seeing this on a make release of 7? > > On 12/5/2007 12:55 PM, Lawrence Farr wrote: > > cc -Os -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith -W > > return-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast- > align > > -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs - > Wredundan > > t-decls -Wno-pointer-sign -c /usr/src/bin/ed/main.c > > *** Error code 1 > > > > Stop in /usr/src/bin/ed. > > *** Error code 1 > > > > Stop in /usr/obj/usr/src/release/fixit_crunch. > > *** Error code 1 > > > > Stop in /usr/src/release. > > *** Error code 1 > > > > Stop in /usr/src/release. > > in.c:106: warning: argument 'argv' might be clobbered by 'longjmp' or > > 'vfork' > > + umount /dev > > > > Been getting it for a week or so now, it's being built on: > > > > 7.0-BETA3 FreeBSD 7.0-BETA3 #0: Mon Nov 26 01:04:55 GMT 2007 > > Are you sure that you are building from RELENG_7 source? It doesn't > have > -Werror defined, IIRC. And HEAD should be fixed by this commit: > http://lists.freebsd.org/pipermail/cvs-src/2007-December/084624.html > > > HTH, > Yuri Got it, was using 7 source, and the release script had "RELEASETAG=." defined later in it. Thanks for the clue! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Anyone else seeing this on a make release of 7?
cc -Os -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -W return-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundan t-decls -Wno-pointer-sign -c /usr/src/bin/ed/main.c *** Error code 1 Stop in /usr/src/bin/ed. *** Error code 1 Stop in /usr/obj/usr/src/release/fixit_crunch. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. in.c:106: warning: argument 'argv' might be clobbered by 'longjmp' or 'vfork' + umount /dev Been getting it for a week or so now, it's being built on: 7.0-BETA3 FreeBSD 7.0-BETA3 #0: Mon Nov 26 01:04:55 GMT 2007 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install of 6.3RC1 on Virtual PC 2007 hangs
On ons, des 05, 2007 at 10:04:30am +1100, Dewayne Geraghty wrote: > The installation of 6.3RC1 hangs at the line > Trying to mount root from ufs:/dev/md0 > > the probes immediately before this were: > md0: Preloaded image 4423680 bytes at 0xc0b47cd4 > ad0: 8195MB at ata0-master WDM2 > acd0: DVDROM at ata1-master PIO4 > > This is being attempted via Virtual PC 2007 on a Core2Duo T5500 with 256MB > allocated to the image, and 8GB to the VDisk. The physical CD has been used > to successfully install on standalone computers, so the burnt image is ok. > > This isn't urgent but should be noted as there may be other virtualisation > instances where RC1 doesn't install as expected. We're happy to perform > other tests as required. We're staging 6.3 on Via C7's, and Intel with > hifn's, and the notebook is used for quick testing of crash/burn work. > I just tested it, and it also hung here at the same spot. Pentium 4, 512MB allocated RAM. I tried both capturing iso image and using the machine cdrom, but neither worked. -- Ulf Lilleengen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
