Re: pkgbase: Missing /etc/master.passwd in FreeBSD-runtime 12-stable pkg
On 1/31/21 12:04 PM, mj-mailingl...@gmx.de wrote: I noticed that my jails, build from a recent pkg base don't start: ... Starting jails: cannot start jail "j6": 7 jail: j6: getpwnam root: No such file or directory jail: j6: /bin/sh /etc/rc: failed . [snip] Just a thought, did you run make distribution DESTDIR= Per ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: STABLE fails since change to Clang 8
On 2019-04-22 00:10, Eugen wrote: I used to build world and kernel every other week. My last successful build of the source tree was version 345754. I believe in the meantime Clang was changed from 7 to 8. World build fails ever since with this: --- [snip] /usr/src/contrib/llvm/tools/clang/lib/Basic/SourceManager.cpp:1195:10: fatal error: 'emmintrin.h' file not found #include ^ 1 error generated. *** [Basic/SourceManager.o] Error code 1 make[4]: stopped in /usr/src/lib/clang/libclang 1 error make[4]: stopped in /usr/src/lib/clang/libclang *** [all_subdir_lib/clang/libclang] Error code 2 make[3]: stopped in /usr/src/lib/clang 1 error make[3]: stopped in /usr/src/lib/clang *** [cross-tools] Error code 2 make[2]: stopped in /usr/src 1 error make[2]: stopped in /usr/src *** [_cross-tools] Error code 2 make[1]: stopped in /usr/src 1 error --- uname -a produces this: FreeBSD main 12.0-STABLE FreeBSD 12.0-STABLE #0 r345754M: Sun Mar 31 10:01:26 PDT 2019 root@main:/home/sys_build/usr/src/amd64.amd64/sys/WORLD amd64 +1 for 11-STABLE and ports too - would be nice if this could be sorted rather quickly. There are six incarnations of emmintrin.h in this system but apparently none is useful: /usr/src/contrib/gcc/config/i386/emmintrin.h /usr/src/contrib/llvm/tools/clang/lib/Headers/emmintrin.h /usr/local/llvm70/lib/clang/7.0.1/include/emmintrin.h /usr/local/llvm80/lib/clang/8.0.0/include/emmintrin.h /usr/local/lib/gcc8/gcc/x86_64-portbld-freebsd11.2/8.3.0/include/emmintrin.h /usr/local/llvm60/lib/clang/6.0.1/include/emmintrin.h https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237461 Thanks, //per ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
OpenSSL version in -STABLE?
As I understand it, there are plans for a major upgrade of OpenSSL in -CURRENT. Will this likely be backported to 11-STABLE or should I prepare switching to 12 when it is ready? Would prefer not to be dependant on the security/openssl port. Thanks, ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: USB GSM still in trouble after upgrade to 11.1-RELEASE-p10
On 05/14/18 16:35, Willem Jan Withagen wrote: > Hi, > > Yesterday evening I upgraded a system to 11.1-RELEASE-p10. > But that sort of upset my GSM-dongle I use for alarming. > > And it did not do that before the upgrade, where I was running -p9. > > > This is what I find repeated at rather high frequency in the logs: > +ugen1.3: at usbus1 > +u3g0 on uhub3 > +u3g0: on usbus1 > +u3g0: Found 2 ports. > +umass0 on uhub3 > +umass0: addr 3> on usbus1 > +umass0: SCSI over Bulk-Only; quirks = 0x > +umass0:3:0: Attached to scbus3 > +(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00 > +(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > +(probe0:umass-sim0:0:0:0): Retrying command > +(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00 > +(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > +(probe0:umass-sim0:0:0:0): Retrying command > +(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00 > +(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > +(probe0:umass-sim0:0:0:0): Retrying command > +(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00 > +(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > +(probe0:umass-sim0:0:0:0): Retrying command > +(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00 > +(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > +(probe0:umass-sim0:0:0:0): Error 5, Retries exhausted > +ugen1.3: at usbus1 (disconnected) > +u3g0: at uhub3, port 2, addr 3 (disconnected) > +u3g0: detached > +umass0: at uhub3, port 2, addr 3 (disconnected) > +umass0: detached > > So when I get home, I'm going to pull the stick. > But what could be going on here? I have identical behavior on a FreeBSD 11.1-STABLE #0 r330526 system after it was restarted today. It used to work with a Huawei E398 but after the reboot it does not, just like your above. Interestingly, I replaced it with a much older Huawei E1750 and that one worked, but only after I rebooted again. With the E398 after a reboot I only see /dev/cuau1, no cuaUX.X If I pull it and replace with E1750 nothing happens If I reboot with the E1750 in place, I get /dev/cuaUX.X Fishy... ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: STABLE-10 does not build
On 2016-04-16 15:42, David Wolfskill wrote: > On Sat, Apr 16, 2016 at 03:30:28PM +0200, Per olof Ljungmark wrote: >> Hi, >> >> Hopefully someone is looking at this? >> > > Ref. <http://docs.FreeBSD.org/cgi/mid.cgi?86oa9a59r3.wl-herbert> > > (After applying the patch in that message, stable/10 @r298100 built for > me, and I'm running it (on my laptop) as I type.) Looks like it is commited too - thanks for fixing it so quickly //per ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
STABLE-10 does not build
Hi, Hopefully someone is looking at this? CC='cc ' mkdep -f .depend -a-DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/groff/src/devices/grotty/../../../../../../contrib/groff/src/include -I/usr/src/gnu/usr.bin/groff/src/devices/grotty/../../../src/include /usr/src/gnu/usr.bin/groff/src/devices/grotty/../../../../../../contrib/groff/src/devices/grotty/tty.cpp --- sbin.depend__D --- /usr/src/sbin/pfctl/pfctl_qstats.c:41:10: fatal error: 'net/altq/altq_fairq.h' file not found #include ^ 1 error generated. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: jail: /etc/rc: cannot create /dev/null: Operation not supported
On 2015-07-18 18:29, James Gritton wrote: On 2015-07-17 11:26, Per olof Ljungmark wrote: On 2015-07-17 01:41, James Gritton wrote: On 2015-07-15 13:52, Per olof Ljungmark wrote: FreeBSD 10.2-PRERELEASE #0 r284949 The jail can be started, but when /etc/rc is executed: root@mar:/ # sh -x /etc/rc + stty status ^T /etc/rc: cannot create /dev/null: Operation not supported + trap : 2 + trap 'echo '\''Boot interrupted'\''; exit 1' 3 + HOME=/ + PATH=/sbin:/bin:/usr/sbin:/usr/bin + export HOME PATH + [ '' = autoboot ] + autoboot=no + _boot=quietstart + /sbin/sysctl -n vfs.nfs.diskless_valid /etc/rc: cannot create /dev/null: Operation not supported ... I have done the procedure several times before but never saw this one before and don't know how to get around it. Ideas anyone? Any recent changes that can show up like the above? Thanks! If it's trying to create /dev/null, I assume that the jail's /dev isn't mounted when /etc/rc is running. Do you have mount.devfs set in the jail.conf, or jail_foo_devfs_enable in rc.conf (depending on your configuration)? For that matter, can you tell if the jail's /dev is mounted? Yes, it's mounted. Because I can set up jails with an identical procedure on other boxes we run I suspect something is wrong with the install so I am starting from scratch with this one. While doing that, I am trying to sort another problem, namely to boot zfs on root on a HP Proliant with a P410 controller, but that is another story. You know, if it was easy it would not be interesting... Thanks! So maybe a little late since you're starting over, but another possibility is the devfs ruleset. If something went wrong in setting that up, you could well have a devfs mounted that shows no devices. True, although I did check the rulesets. However, since this is a box that will go into production I did not want to take any chances in case we missed something that might show up in other places later. ___ 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: jail: /etc/rc: cannot create /dev/null: Operation not supported
On 2015-07-17 01:41, James Gritton wrote: On 2015-07-15 13:52, Per olof Ljungmark wrote: FreeBSD 10.2-PRERELEASE #0 r284949 The jail can be started, but when /etc/rc is executed: root@mar:/ # sh -x /etc/rc + stty status ^T /etc/rc: cannot create /dev/null: Operation not supported + trap : 2 + trap 'echo '\''Boot interrupted'\''; exit 1' 3 + HOME=/ + PATH=/sbin:/bin:/usr/sbin:/usr/bin + export HOME PATH + [ '' = autoboot ] + autoboot=no + _boot=quietstart + /sbin/sysctl -n vfs.nfs.diskless_valid /etc/rc: cannot create /dev/null: Operation not supported ... I have done the procedure several times before but never saw this one before and don't know how to get around it. Ideas anyone? Any recent changes that can show up like the above? Thanks! If it's trying to create /dev/null, I assume that the jail's /dev isn't mounted when /etc/rc is running. Do you have mount.devfs set in the jail.conf, or jail_foo_devfs_enable in rc.conf (depending on your configuration)? For that matter, can you tell if the jail's /dev is mounted? - Jamie Yes, it's mounted. Because I can set up jails with an identical procedure on other boxes we run I suspect something is wrong with the install so I am starting from scratch with this one. While doing that, I am trying to sort another problem, namely to boot zfs on root on a HP Proliant with a P410 controller, but that is another story. You know, if it was easy it would not be interesting... Thanks! ___ 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
jail: /etc/rc: cannot create /dev/null: Operation not supported
FreeBSD 10.2-PRERELEASE #0 r284949 The jail can be started, but when /etc/rc is executed: root@mar:/ # sh -x /etc/rc + stty status ^T /etc/rc: cannot create /dev/null: Operation not supported + trap : 2 + trap 'echo '\''Boot interrupted'\''; exit 1' 3 + HOME=/ + PATH=/sbin:/bin:/usr/sbin:/usr/bin + export HOME PATH + [ '' = autoboot ] + autoboot=no + _boot=quietstart + /sbin/sysctl -n vfs.nfs.diskless_valid /etc/rc: cannot create /dev/null: Operation not supported ... I have done the procedure several times before but never saw this one before and don't know how to get around it. Ideas anyone? Any recent changes that can show up like the above? Thanks! //per ___ 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
The shutdown bug?
As described in earlier reports, 9-STABLE sometimes cannot halt or reboot properly. FreeBSD 9.1-PRERELEASE #0 r241866: Mon Oct 22 16:28:47 CEST 2012 All ZFS file system, no NFS mounts. The problem occurs after updating sources and rebuilding world for some reason the I suspect is connected to the file system. shutdown -r now or halt -p will stop after Syncing discs forever. It is seen here on various HP boxes, DL360 G4, G5, XW6600 are examples. Issuing a shutdown -n -o -r now works however and I assume this is not too harmful with ZFS? Setting sysctl hw.usb.no_shutdown_wait=1 does NOT fix the problem as described in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/167685 Should I file another bug or add to the existing? Would it be useful to build a debug kernel, if yes, including what? Thanks! //per ___ 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: The shutdown bug?
On 2012-10-23 19:41, jb wrote: Per olof Ljungmark peo at intersonic.se writes: ... Setting sysctl hw.usb.no_shutdown_wait=1 does NOT fix the problem as described in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/167685 ... There is another one: http://www.freebsd.org/cgi/query-pr.cgi?pr=172952cat= jb Thanks, I'll add my experiences to that one. ___ 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: The shutdown bug?
On 10/23/12 21:44, Andriy Gapon wrote: on 23/10/2012 21:38 Per olof Ljungmark said the following: On 2012-10-23 19:41, jb wrote: Per olof Ljungmark peo at intersonic.se writes: ... Setting sysctl hw.usb.no_shutdown_wait=1 does NOT fix the problem as described in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/167685 ... There is another one: http://www.freebsd.org/cgi/query-pr.cgi?pr=172952cat= jb Thanks, I'll add my experiences to that one. I've just posted another followup to that PR. If you could do some debugging that would be great. Building a debugging kernel now, we'll see tomorrow if it works out. Tested an updated HP DL380 G5 all ZFS before leaving work and it was the same, no reboot. ___ 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: Thinkpad X61s cannot boot 9.1-BETA1
On 2012-08-27 19:54, John Baldwin wrote: On Sunday, August 26, 2012 6:59:22 pm Martin Dieringer wrote: On Sun, 26 Aug 2012, Per olof Ljungmark wrote: On 08/26/12 18:37, Kurt Jaeger wrote: Hi! On our X61s's setting 'debug.acpi.disabled=hostres' does not change the inability to boot 9-BETA1, 9-RC1 or -current. I tested 9.1-RC1 on X61, and it worked without any troubles. Yes, it does on this one too if I install a mechanical disk. The problem is related to installing on a SSD drive, Kingston SSDNow SV200S37A/128G. This must be related to a change in the base system some time between 9.0-RELEASE and -BETA1 as 9.0 runs and installs fine. Perhaps someone could suggest anther SSD drive with equal capacity that works? debug.acpi.disabled=hostres fixed it for me on T61 and T410 with normal HD and (older) SSD (OCZ Summit) FreeBSD 9.1-PRERELEASE #16: Tue Aug 21 Can you get a verbose dmesg both with and without the hostres setting? OK, will post tomorrow, a quick check with debug.acpi.disabled=hostres yields same output excluding the ata0: reset ... lines. ___ 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: Thinkpad X61s cannot boot 9.1-BETA1
On 08/21/12 21:09, John Baldwin wrote: On Tuesday, August 21, 2012 1:50:27 pm Martin Dieringer wrote: On Tue, 31 Jul 2012, John Baldwin wrote: On Friday, July 20, 2012 10:11:33 am jb wrote: Did anyone else experience this? With 9.1-BETA1 the boot process freezes, among the last lines with verbose boot are acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times after this, dead. ... set debug.acpi.disabled=hostres boot Or, put the following line into /boot/loader.conf: debug.acpi.disabled=hostres ... Anyway, regardless of this attempt, file a PR# for 9.1-BETA1. Please try this and let me know if it works. The bugs that I knew of related to hostres should be fixed in 9.1, so if there are still problems I'd like to know about it. this seems to work on a T410, at least it can boot the latest USB-image now. T61 has the same problem, btw. So the hostres hint fixes your T410 on 9.1 that was broken without it? On our X61s's setting 'debug.acpi.disabled=hostres' does not change the inability to boot 9-BETA1, 9-RC1 or -current. What does fix it however, is to change the Kingston SSD drive to a standard mechanical one. This is verified on three different X61s's, see http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/170487 Is there something else I could try or should I just switch drive and be fine with it? I'm happy to try anything you suggest. Thanks, ___ 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: Thinkpad X61s cannot boot 9.1-BETA1
On 08/26/12 18:37, Kurt Jaeger wrote: Hi! On our X61s's setting 'debug.acpi.disabled=hostres' does not change the inability to boot 9-BETA1, 9-RC1 or -current. I tested 9.1-RC1 on X61, and it worked without any troubles. Yes, it does on this one too if I install a mechanical disk. The problem is related to installing on a SSD drive, Kingston SSDNow SV200S37A/128G. This must be related to a change in the base system some time between 9.0-RELEASE and -BETA1 as 9.0 runs and installs fine. Perhaps someone could suggest anther SSD drive with equal capacity that works? Thanks, ___ 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: Thinkpad X61s cannot boot 9.1-BETA1
On 2012-07-20 08:02, John Marshall wrote: On Thu, 19 Jul 2012, 11:14 +0200, Per olof Ljungmark wrote: Did anyone else experience this? With 9.1-BETA1 the boot process freezes, among the last lines with verbose boot are acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times after this, dead. What is supposed to happen in the next stage? This laptop worked fine with 9-STABLE to at least february. This morning I csup'd RELENG_9, built, and upgraded my ThinkPad T43 from 9.0-RELEASE-p3 with no problem. See dmesg output below. I do realize that a ThinkPad T43 is not a ThinkPad X61 but, not knowing how similar or different they may be, I thought I'd post a reply anyway. My kernel config includes the following two drivers which may be relevant (particularly acpi_ibm): they have been in the config for a number of years. device acpi_ibm device acpi_video snip X61s is rather different from T43 so that might explain why. I have tried various variations of modules but there is no difference. RELENG-9 boots fine 9-BETA1 not 10-CURRENT not I'll stay at RELENG-9 for the time being and see if anything comes up that sheds light on this. Thanks, ___ 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
Thinkpad X61s cannot boot 9.1-BETA1
Hi, Did anyone else experience this? With 9.1-BETA1 the boot process freezes, among the last lines with verbose boot are acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times after this, dead. What is supposed to happen in the next stage? This laptop worked fine with 9-STABLE to at least february. //per ___ 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: Thinkpad X61s cannot boot 9.1-BETA1
On 07/19/12 20:22, jb wrote: Per olof Ljungmarkpeoat intersonic.se writes: Hi, Did anyone else experience this? With 9.1-BETA1 the boot process freezes, among the last lines with verbose boot are acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times after this, dead. What is supposed to happen in the next stage? This laptop worked fine with 9-STABLE to at least february. Try Google search: acpi_acad0: acline initialization done, tried 1 times for example http://forums.freebsd.org/archive/index.php/t-12194.html ... boot with disable acpi selection Tried ALL boot options, none worked. For example, if I try disable acpi it will stop at no event timer available. ___ 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: Why Are You Using FreeBSD?
On 05/30/12 20:20, David Chisnall wrote: Hi Everyone, This is off-topic, so please feel free to disregard it, but I'm sending it to this list in the hope that it will reach a largish number of users. I am currently looking at updating some of our advocacy material (which advertises exciting new features like SMP support), and before I do I'd like to get a better feel for why the rest of you are using FreeBSD. If you had to list the three things you most like about FreeBSD, which would you pick? Are they the same as when you first started using it? Without going into detail,BSD has served our company extremely well for over fifteen years for all server purposes we need. File server, mail, MX, web, routing/firewalls you name it. Never let us down, the stability is just out of this world, the docs are excellent and the people great. So, 1. Stability 2. Ease of upgrades 3. The community and developers A big thank you to all that keeps us running! //per ___ 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: cvsup.de.FreeBSD.org out of sync? (was: make buildkernel KERNCONF=GENERIC fails)
Ruben van Staveren wrote: On 26 May 2009, at 22:38, Christian Walther wrote: it finished successfully. From my point of view it appears that cvsup.de.freebsd.org is out of sync. cvsup.de.freebsd.org is definitely out of sync. I had build errors which only went away after switching to a different cvsup server Same here, a week ago. -- per ___ 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
kernel compile fails in machdep.c
Latest stable sources, machdep.c is $FreeBSD: src/sys/i386/i386/intr_machdep.c,v 1.29.2.7 2009/05/19 22:07:54 jhb Exp $ cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/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 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/i386/i386/intr_machdep.c cc1: warnings being treated as errors /usr/src/sys/i386/i386/intr_machdep.c: In function 'intr_register_source': /usr/src/sys/i386/i386/intr_machdep.c:136: warning: passing argument 4 of 'intr_event_create' makes pointer from integer without a cast /usr/src/sys/i386/i386/intr_machdep.c:136: warning: passing argument 7 of 'intr_event_create' from incompatible pointer type /usr/src/sys/i386/i386/intr_machdep.c:136: warning: passing argument 8 of 'intr_event_create' from incompatible pointer type /usr/src/sys/i386/i386/intr_machdep.c: In function 'intr_execute_handlers': /usr/src/sys/i386/i386/intr_machdep.c:261: warning: implicit declaration of function 'intr_event_handle' /usr/src/sys/i386/i386/intr_machdep.c:261: warning: nested extern declaration of 'intr_event_handle' *** Error code 1 -- per ___ 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: kernel compile fails in machdep.c
John Baldwin wrote: On Thursday 21 May 2009 4:15:54 am Per olof Ljungmark wrote: Latest stable sources, machdep.c is $FreeBSD: src/sys/i386/i386/intr_machdep.c,v 1.29.2.7 2009/05/19 22:07:54 jhb Exp $ cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/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 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/i386/i386/intr_machdep.c cc1: warnings being treated as errors /usr/src/sys/i386/i386/intr_machdep.c: In function 'intr_register_source': /usr/src/sys/i386/i386/intr_machdep.c:136: warning: passing argument 4 of 'intr_event_create' makes pointer from integer without a cast /usr/src/sys/i386/i386/intr_machdep.c:136: warning: passing argument 7 of 'intr_event_create' from incompatible pointer type /usr/src/sys/i386/i386/intr_machdep.c:136: warning: passing argument 8 of 'intr_event_create' from incompatible pointer type /usr/src/sys/i386/i386/intr_machdep.c: In function 'intr_execute_handlers': /usr/src/sys/i386/i386/intr_machdep.c:261: warning: implicit declaration of function 'intr_event_handle' /usr/src/sys/i386/i386/intr_machdep.c:261: warning: nested extern declaration of 'intr_event_handle' *** Error code 1 I think you must have some files not in sync. It compiled before commit and the tinderbox has not reported any errors after the commit. Yes, I just saw this. The original sources were fetched from cvsup.de.freebsd.org (twice, same result), then I switched to cvsup.freebsd.org and got the right version. I would like to notify the admins of .de but unsure of how to. Thanks, -- per ___ 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: CAM Status: SCSI Status Error on 7.2-RELEASE
Yani Karydis wrote: Hello, Since upgrading to 7.2-RELEASE, dmesg displays the following after booting the system. (probe3:ahc0:0:3:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe3:ahc0:0:3:0): CAM Status: SCSI Status Error (probe3:ahc0:0:3:0): SCSI Status: Check Condition (probe3:ahc0:0:3:0): UNIT ATTENTION asc:29,0 (probe3:ahc0:0:3:0): Power on, reset, or bus device reset occurred (probe3:ahc0:0:3:0): Retrying Command (per Sense Data) (probe3:ahc0:0:3:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe3:ahc0:0:3:0): CAM Status: SCSI Status Error (probe3:ahc0:0:3:0): SCSI Status: Check Condition (probe3:ahc0:0:3:0): NOT READY asc:3a,0 (probe3:ahc0:0:3:0): Medium not present (probe3:ahc0:0:3:0): Unretryable error sa0 at ahc0 bus 0 target 3 lun 0 sa0: HP Ultrium 1-SCSI N2CG Removable Sequential Access SCSI-3 device sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) snip FWIW, same here, 7.2-PRERELEASE #0: Thu Apr 16 08:42:45 CEST 2009 amd64 and HP Ultrium drive. Did not notice any harm though. -- per ___ 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
named: confusing error message
7.1-PRERELEASE #0: Sun Oct 19 13:14:29 CEST 2008 amd64, sources from mid-day yesterday UTC. Named died with the following error: Oct 20 03:24:18 named[635]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/buffer.c:85: REQUIREb) != ((void *)0)) (((const isc__magic_t *)(b))-magic == (0x42756621U failed Hardware error or bug? -- per ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
is iwi supposed to work on 7-STABLE?
Hi, Have Thinkpad T42 with 2200 wireless that USED to work with if_iwi and 7-STABLE, now regardless of what I do I cannot associate with access points (works with XP). Are there any changes made that I cannot see during the last few months that changed operation? Have setup loader.conf according to man page. Thanks for any hints, --per ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: rtfree - any work done currently on this?
Hi, I wonder if any work is done on http://www.freebsd.org/cgi/query-pr.cgi?pr=117913 if it is I'll be happy to test patches and/or suggestions or provide access to a box for debugging. Thanks, --per rtfree: 0xc5732d20 has 1 refs ssppiinn lloocckk 00xxcc5500ff22a20800 ((ttuurrnnssttiillee lloocckk)) hheelldd bbyy 00xxcc5597868600 ((ttiidd 11002154)) tt lloonngg panic: spin lock held too long cpuid = 1 KDB: enter: panic [thread pid 16 tid 100014 ] Stopped at kdb_enter+0x32: leave db wh Tracing pid 16 tid 100014 td 0xc5117660 kdb_enter(c0a9c7e0,1,c0a9b6b4,e3cb7b7c,1,...) at kdb_enter+0x32 panic(c0a9b6b4,c5119880,c0aa0958,c5119880,186b9,...) at panic+0x124 _mtx_lock_spin_failed(1,19,c0aa0984,cb,19,...) at _mtx_lock_spin_failed+0x51 _thread_lock_flags(c5119880,10,c0aa0984,cb,1,...) at _thread_lock_flags+0xc7 propagate_priority(c0bbd470,0,c0aa0984,2e2,c50f2c80,...) at propagate_priority+0xe0 turnstile_wait(c50f2c80,c55c4cc0,0,17a,c5867d08,...) at turnstile_wait+0x48c _mtx_lock_sleep(c5867d08,c5117660,0,c0ab2afe,1b6,...) at _mtx_lock_sleep+0x15a _mtx_lock_flags(c5867d08,0,c0ab2afe,1b6,3d2a1,...) at _mtx_lock_flags+0xef tcp_timer_rexmt(c58698ac,0,c0a9d9f9,ef,12,...) at tcp_timer_rexmt+0x96 softclock(0,0,c0a993e9,471,c515e364,...) at softclock+0x266 ithread_loop(c5113290,e3cb7d38,c0a9915d,2ea,c515f550,...) at ithread_loop+0x1b5 fork_exit(c0732ea0,c5113290,e3cb7d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xe3cb7d70, ebp = 0 --- db ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: rtfree - any work done currently on this?
Ivan Voras wrote: Per olof Ljungmark wrote: Hi, I wonder if any work is done on http://www.freebsd.org/cgi/query-pr.cgi?pr=117913 if it is I'll be happy to test patches and/or suggestions or provide access to a box for debugging. Last I've heard about it is that a fix was committed to 7-CURRENT. Then I think something else was fixed - the issues we see still exists as of yesterday's sources. Thanks, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: Re: kern/118044: panic: spin lock held too long]
Original Message Subject: Re: kern/118044: panic: spin lock held too long Date: Wed, 14 Nov 2007 15:20:01 GMT From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED] To: Per olof Ljungmark [EMAIL PROTECTED] Thank you very much for your problem report. It has the internal identification `kern/118044'. The individual assigned to look at your report is: freebsd-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=118044 Category: kern Responsible:freebsd-bugs Synopsis: panic: spin lock held too long Arrival-Date: Wed Nov 14 15:20:01 UTC 2007 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
blkfree bug
Hi, I just got bitten by something that looks like the blkfree bug as discussed here: http://www.freebsd.org/cgi/mid.cgi?db=irt[EMAIL PROTECTED] Reading the thread seems to reveal disabling softupdates will make the problem go away. I assume from http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/116913 that the bug is still present? Any patches available? The link in the PR is dead at least from where I am. I have dump available if someone is interested in more information. 7.0-PRERELEASE #0: Sun Oct 14 08:03:58 CEST 2007 Thanks, --per ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI warning msgs during boot - significance?
Hi, This unit is supposedly going to be my new home ws, are the below acpi errors something that I need to worry about? Thanks, --per Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-BETA1 #0: Tue Oct 23 18:23:25 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WEIR Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3200.13-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x641dSSE3,RSVD2,MON,DS_CPL,CNXT-ID,CX16,xTPR AMD Features=0x2000LM real memory = 1073676288 (1023 MB) avail memory = 1037070336 (989 MB) ACPI APIC Table: COMPAQ TUMWATER ACPI Warning (tbfadt-0324): FADT (revision 3) is longer than ACPI 2.0 version, truncating length 0x10C to 0xF4 [20070320] ACPI Error (tbfadt-0516): 32/64X address mismatch in Gpe0Block: [ F828] [ 0 1F030], using 64X [20070320] ACPI Error (tbutils-0314): Null physical address for ACPI table [(null)] [20070320] ACPI Error (tbutils-0314): Null physical address for ACPI table [(null)] [20070320] ACPI Error (tbutils-0314): Null physical address for ACPI table [(null)] [20070320] ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: COMPAQ CPQ0063 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xf808-0xf80b on acpi0 cpu0: ACPI CPU on acpi0 p4tcc0: CPU Frequency Thermal Control on cpu0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci32: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0 pci1: ACPI PCI bus on pcib2 pci0:1:0:0: bad VPD cksum, remain 14 bge0: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4001 mem 0xf820-0xf820 irq 16 at device 0.0 on pci1 miibus0: MII bus on bge0 brgphy0: BCM5750 10/100/1000baseTX PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:12:79:de:50:6f bge0: [ITHREAD] pcib3: ACPI PCI-PCI bridge at device 4.0 on pci0 pci64: ACPI PCI bus on pcib3 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xf000-0xf7ff,0xf810-0xf810 irq 16 at device 0.0 on pci64 vgapci1: VGA-compatible display mem 0xf811-0xf811 at device 0.1 on pci64 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0x5440-0x545f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0x5460-0x547f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0x5480-0x549f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0x54a0-0x54bf irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xf830-0xf83003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb4 uhub4: 8 ports with 8 removable, self powered pcib4: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib4 mpt0: LSILogic 1030 Ultra4 Adapter port 0x4000-0x40ff mem 0xf800-0xf801,0xf802-0xf803 irq 18 at device 9.0 on pci2 mpt0: [ITHREAD] mpt0: MPI Version=1.2.12.0 isab0: PCI-ISA bridge at device 31.0 on
Re: 7.0-BETA1
rihad wrote: How risky is it to start using 7.0-BETA1 in production, with the intention of upgrading to release as soon as possible? Thanks. We've used 7-CURRENT since January on a couple of production boxes and had very few disasters, well, none, but a couple of issues. Risky is a relative term really, but if you ask me I'd say the risk is rather low. But: TEST FIRST! --per ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade confusion
Hi, Running portupgrade on RELENG_7, got this whlie updating net-snmp and I have no idea what what this means. System ran -CURRENT from Jan 16 before upgrade to todays sources (RELENG_7): pkgdb -F Fatal error F'aThread is not system scope. t'a la etr rloirn e' Thread is not system scope. 3'1 6a ti nl ifniel e3 1/usr/src/lib/libpthread/thread/thr_sig.c6 (ienr rfniol e= /usr/src/lib/libpthread/thread/thr_sig.c2 )( errno = 2) Abort (core dumped) Thanks, Per olof ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade confusion
Per olof Ljungmark wrote: Hi, Running portupgrade on RELENG_7, got this whlie updating net-snmp and I have no idea what what this means. System ran -CURRENT from Jan 16 before upgrade to todays sources (RELENG_7): pkgdb -F Fatal error F'aThread is not system scope. t'a la etr rloirn e' Thread is not system scope. 3'1 6a ti nl ifniel e3 1/usr/src/lib/libpthread/thread/thr_sig.c6 (ienr rfniol e= /usr/src/lib/libpthread/thread/thr_sig.c2 )( errno = 2) Abort (core dumped) Rebuilding ruby and ruby-bdb fixed it. But the error was quite funny no? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
buildworld failures on STABLE
On a remote machine currently with RELENG-6 from 20th. June, with STABLE sources from this morning I get build failures in contrib/ similar to: cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/usr/obj/usr/src/tmp/usr\ -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DHAVE_CONFIG_H -DTARGET_NAME=\i386-undermydesk-freebsd\ -DIN_GCC -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c: In function `pre_edge_rev_lcm': /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c:801: internal compiler error: Segmentation fault: 11 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Would this indicate a hardware (memory) problem? Any way to test remotely? Thanks. Per olof ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld failures on STABLE
Eugene Grosbein wrote: On Sun, Oct 07, 2007 at 11:40:11AM +0200, Roland Smith wrote: On a remote machine currently with RELENG-6 from 20th. June, with STABLE sources from this morning I get build failures in contrib/ similar to: snip /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c:801: internal compiler error: Segmentation fault: 11 snip Would this indicate a hardware (memory) problem? Yes. The compiler dying with signal 11 is a typical memory problem. Any way to test remotely? There are memory test applications like memtest86+ (http://www.memtest.org/). You have to boot from it, but it does support a console on a serial port. There is also ports/sysutils/memtest that may be run from multiuser if one manages to build it with broken memory :-) Or it's possible to install a package. One problem with running such application with OS loaded is that kernel places strict limit to amount of memory that user-level application may lock. There is a PR with a patch that allows to raise the limit so memtest could test most part of free memory: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/114654 Thanks for the memtest advice, I ran it and memory is definitely hosed. Sigh, that means 400 kilometers of travel... Per olof ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: All routes to freebsd are dead
Chris H. wrote: Greetings, Lately I've been finding it difficult, to impossible to reach freebsd.org. (hope this message makes it) At any rate, no matter my location; all routes to freebsd.org appear to be dead. From my home base, the route to freebsd.org appears to be provided by Yahoo # traceroute www.freebsd.org ... 8 ix-6-2.core3.PDI-PaloAlto.Teleglobe.net (207.45.213.130) 101.882 ms 101.642 ms 122.385 ms 9 g-0-0-0-p150.msr2.sp1.yahoo.com (216.115.107.73) 103.554 ms g-1-0-0-p140.msr1.sp1.yahoo.com (216.115.107.53) 101.487 ms g-1-0-0-p150.msr2.sp1.yahoo.com (216.115.107.77) 103.430 ms 10 ge-1-47.bas-b2.sp1.yahoo.com (209.131.32.53) 102.561 ms ge-1-41.bas-b1.sp1.yahoo.com (209.131.32.25) 103.646 ms 102.476 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * # From my end, it seems Yahoo is doing freebsd.org a great disservice. Bouncing the routers and switches here have no (positive) affect. Nor does dumping caches, and restarting the nameservers. I noticed earlier on, someone else mentioning troubles connecting to freebsd.org. Can anyone shed any light on this? Thank you for all your time and consideration. Same here... traceroute to www.freebsd.org (69.147.83.33), 64 hops max, 40 byte packets 4 lim-core-1.pos0-0-0.swip.net (130.244.52.162) 8.511 ms 8.544 ms 8.561 ms 5 nyc9-core-2.pos2-0.swip.net (130.244.194.205) 97.432 ms 97.249 ms 97.703 ms 6 bas1-m.nyc.yahoo.com (198.32.118.24) 97.771 ms 97.685 ms 97.699 ms 7 ge-2-3-4-p809.pat2.pao.yahoo.com (216.115.98.53) 176.651 ms ge-1-3-4-p154.pat2.pao.yahoo.com (216.115.96.52) 164.6 ms ge-3-3-4-p456.pat2.pao.yahoo.com (216.115.97.198) 170.86 ms 8 g-1-0-0-p141.msr1.sp1.yahoo.com (216.115.107.55) 164.431 ms g-1-0-0-p151.msr2.sp1.yahoo.com (216.115.107.79) 171.132 ms 177.407 ms 9 ge-1-41.bas-b1.sp1.yahoo.com (209.131.32.25) 170.953 ms ge-1-45.bas-b1.sp1.yahoo.com (209.131.32.41) 171.170 ms ge-1-43.bas-b1.sp1.yahoo.com (209.131.32.29) 177.23 ms 10 * * * 11 * * * ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Firefox keeps beeping at me ...
Glenn Becker wrote: All - I've been away from FreeBSD for some time and have been updating my installation, getting used to the ways of portupgrade, etc. Have noticed that Firefox keeps emitting what sound like console beeps - I haven't established much of a pattern for these though it always happens when I close the app. Is there a way to kill these? Apologies in advance if this is a dopey question. Obviously more an annoyance than anything. perhaps -questions is more appropriate... Anyway, that makes two of us - mine beeps too - when sending and reading mails. No idea why though, sorry. Anyone? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6-STABLE locks solid - current ok, why?
Hi, Got a testbed Proliant DL380G2, internal SmartArray 5i disabled, have SmartArray 5300 with 6 disks. Installed 6.1-REL last week, rebuilt to -STABLE three times since without a problem. However, when I try to add various (random) applications the box locks up solid during configure or make. Apps tested are postfix, jdk15, OpenOffice-2.0 and more. When it hangs the only thing remaining is power cycling, no keyboard access possible. What puzzles me here is that now I installed -CURRENT from yesterday on same box without any other changes and it works like charm, so far I'm through building close to 50 ports including kde with dependencies. Next step I guess is to go back to RELENG and check again. Meanwhile, does anyone out there have an idea where I should look? This box is going into production and I'm not brave enough to run -CURRENT... Thanks, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6-STABLE locks solid - current ok, why?
Daniel Bond wrote: On 22:22 Mon 24 Jul, Per olof Ljungmark wrote: Hi, Got a testbed Proliant DL380G2, internal SmartArray 5i disabled, have SmartArray 5300 with 6 disks. Installed 6.1-REL last week, rebuilt to -STABLE three times since without a problem. However, when I try to add various (random) applications the box locks up solid during configure or make. Apps tested are postfix, jdk15, OpenOffice-2.0 and more. When it hangs the only thing remaining is power cycling, no keyboard access possible. What puzzles me here is that now I installed -CURRENT from yesterday on same box without any other changes and it works like charm, so far I'm through building close to 50 ports including kde with dependencies. Next step I guess is to go back to RELENG and check again. Meanwhile, does anyone out there have an idea where I should look? This box is going into production and I'm not brave enough to run -CURRENT... Hi, try to disable ACPI. It can be usefull for reading CPU temperature and fan speeds, but has no real function on a server. It's mostly usefull for power managment, supend and resume support. From the handbook: Most system hangs are a result of lost interrupts or an interrupt storm. Chipsets have a lot of problems based on how the BIOS configures interrupts before boot, correctness of the APIC (MADT) table, and routing of the System Control Interrupt (SCI). Interrupt storms can be distinguished from lost interrupts by checking the output of vmstat -i and looking at the line that has acpi0. If the counter is increasing at more than a couple per second, you have an interrupt storm. If the system appears hung, try breaking to DDB (CTRL+ALT+ESC on console) and type show interrupts. Your best hope when dealing with interrupt problems is to try disabling APIC support with hint.apic.0.disabled=1 in loader.conf Sorry, I should have mentioned that I tried both ways with same outcome. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6-STABLE locks solid - current ok, why?
The 5300 have a battery backed up cache, I guess I should try to run the box off the 5i to check. Have several 360/380 G1/2/3's here too and never saw this before. I did: * Installed hw; iLO card + one Intel em0 + the 5300 * Booted 6.1-REL CD, installed base system including ports tree and sources * pkg_add -r cvsup-without-gui * fetched 6-STABLE sources * Edit the kernel config (took out 486/586, added SMP/APIC) * rebuilt and installed world (I usually do this a few times over to check for hardware problems) * Installed postfix, that worked ok. * Next app (don't remeber which one sorry) hung the box * fetched 6-STABLE sources again * rebuilt and installed world, worked fine * tried again to complie apps, no joy. Hangs at random places, no error messages, just locks. * fetched 6-STABLE sources again * rebuilt and installed world, worked fine and finally, fetched -CURRENT, rebuilt and now everything is just great. ACPI is enabled. Reason I'm running -STABE is that I expect this one to go into production about the time 6.2 is released. Thanks, Mark Saad wrote: Hello I use many 380's here G2 G3 and G4's and I have not see this yet . I am currently using a G3 w/o any issues with RELENG_6. This box is a jumpstart and buildmaster for my office and this is the DL I use 6.1 on the most. As for the G2 I moved away from them for the most part, but I have one here in my office I could check out if you have a list of what you did. I have two questions for you first, Why are you using the SA5300 , and are you running famd or ganim on the server; or a nfs client attached to the server ? Per olof Ljungmark wrote: Hi, Got a testbed Proliant DL380G2, internal SmartArray 5i disabled, have SmartArray 5300 with 6 disks. Installed 6.1-REL last week, rebuilt to -STABLE three times since without a problem. However, when I try to add various (random) applications the box locks up solid during configure or make. Apps tested are postfix, jdk15, OpenOffice-2.0 and more. When it hangs the only thing remaining is power cycling, no keyboard access possible. What puzzles me here is that now I installed -CURRENT from yesterday on same box without any other changes and it works like charm, so far I'm through building close to 50 ports including kde with dependencies. Next step I guess is to go back to RELENG and check again. Meanwhile, does anyone out there have an idea where I should look? This box is going into production and I'm not brave enough to run -CURRENT... Thanks, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libc bug with nsswitch?
Uwe Laverenz wrote: Hi, there seems to be a problem with RELENG_6 in environments where nss_ldap is used for user- and group-lookups. The problem affects different ports that don't have very much in common, so I guess there might be a bug in FreeBSD's libc, because that's the place, where the name-sevices are handled (correct me if I'm wrong). Two examples that are reproduceable here on various machines: 1. emulators/linux_base-8: When nss_ldap is enabled in /etc/nsswitch.conf, the installation of the port fails: [snip] ... var/tmp/rpm-tmp.41237: line 11: /dev/null: No such file or directory var/tmp/rpm-tmp.41237: line 12: /dev/null: No such file or directory Assertion failed: (cfg-ldc_uris[__session.ls_current_uri] != NULL), function do_init, file ldap-nss.c, line 1245. Abort trap (core dumped) *** Error code 134 2. PHP4(5)/PEAR This was also reported by two other users, both are using nss_ldap but have PHP5 instead of PHP4. With nss_ldap enabled, the use of at least two php-modules (imagick, xslt) lead to a segmentation fault in php4, e.g. when trying to install an additional pear-module: ... A third example: My home workstation uses KDE and is also a Samba BDC. With ldap-enabled nsswitch.conf, if I click on the /home folder in Konqeror I get a message box The process for the file protocol died unexpectedly, also in the starting terminal I get Assertion failed: (cfg-ldc_uris[__session.ls_current_uri] != NULL), function do _init, file ldap-nss.c, line 1245. kioslave: ### CRASH ## protocol = file pid = 72414 signal = 6 Identical to the above, everything is find without ldap in nsswitch.conf. Currently I'm on 6.1-PRERELEASE #0: Wed Feb 22. Per olof ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: smb_ntencrypt: password encryption is not available #2
Per olof Ljungmark wrote: Well, options NETSMBCRYPTO options NETSMB did not work out very well: Do I need anything else here? smb_usr.o(.text+0x4ad):/usr/src/sys/netsmb/smb_usr.c:274: undefined reference to `md_get_mem' smb_usr.o(.text+0x4fe): In function `smb_cpdatain': /usr/src/sys/netsmb/smb_usr.c:291: undefined reference to `mb_init' smb_usr.o(.text+0x513):/usr/src/sys/netsmb/smb_usr.c:294: undefined reference to `mb_put_mem' smb_usr.o(.text+0x63a): In function `smb_usr_t2request': /usr/src/sys/netsmb/smb_usr.c:340: undefined reference to `md_get_mem' smb_usr.o(.text+0x689):/usr/src/sys/netsmb/smb_usr.c:353: undefined reference to `md_get_mem' *** Error code 1 Stop in /usr/obj/usr/src/sys/IKO. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ___ apparently the answer was to use options NETSMBCRYPTO only. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: smb_ntencrypt: password encryption is not available
Per olof Ljungmark wrote: Rebuilt from 6-STABLE sources just now and mount_smbfs fails with the following message: mount_smbfs: unable to open connection: syserr = Authentication error smb_encrypt: password encryption is not available smb_ntencrypt: password encryption is not available I'm just now making a new kernel with options NETSMBCRYPTO options NETSMB to see if it helps. This machine worked like charm before, is there a change somewhere? I'll answer myself then... I still don't know why I needed to make a kernel with options NETSMBCRYPTO but it did solve the problem. There must be a change somewhere, either I did it here or in the system. Other pre-02/17/06 systems here are ok without this kernel option. Sigh. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
smb_ntencrypt: password encryption is not available
Rebuilt from 6-STABLE sources just now and mount_smbfs fails with the following message: mount_smbfs: unable to open connection: syserr = Authentication error smb_encrypt: password encryption is not available smb_ntencrypt: password encryption is not available I'm just now making a new kernel with options NETSMBCRYPTO options NETSMB to see if it helps. This machine worked like charm before, is there a change somewhere? Thanks, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
smb_ntencrypt: password encryption is not available #2
Well, options NETSMBCRYPTO options NETSMB did not work out very well: Do I need anything else here? qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -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 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror vnode_if.c touch hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/usr/obj/usr/src/make.i386/make sh /usr/src/sys/conf/newvers.sh IKO cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -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 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror vers.c linking kernel.debug smb_conn.o(.text+0xa1b): In function `smb_vc_create': /usr/src/sys/netsmb/smb_conn.c:443: undefined reference to `iconv_open' smb_conn.o(.text+0xa3f):/usr/src/sys/netsmb/smb_conn.c:446: undefined reference to `iconv_open' smb_conn.o(.text+0xa66):/usr/src/sys/netsmb/smb_conn.c:450: undefined reference to `iconv_open' smb_conn.o(.text+0xa84):/usr/src/sys/netsmb/smb_conn.c:454: undefined reference to `iconv_open' smb_conn.o(.text+0xb98): In function `smb_vc_free': /usr/src/sys/netsmb/smb_conn.c:489: undefined reference to `iconv_close' smb_conn.o(.text+0xbb0):/usr/src/sys/netsmb/smb_conn.c:491: undefined reference to `iconv_close' smb_conn.o(.text+0xbc8):/usr/src/sys/netsmb/smb_conn.c:493: undefined reference to `iconv_close' smb_conn.o(.text+0xbe0):/usr/src/sys/netsmb/smb_conn.c:495: undefined reference to `iconv_close' smb_iod.o(.text+0x550): In function `smb_iod_sendrq': /usr/src/sys/netsmb/smb_iod.c:249: undefined reference to `mb_fixhdr' smb_iod.o(.text+0x8a7): In function `smb_iod_recvall': /usr/src/sys/netsmb/smb_iod.c:346: undefined reference to `md_initm' smb_iod.o(.text+0x8be):/usr/src/sys/netsmb/smb_iod.c:349: undefined reference to `md_append_record' smb_rq.o(.text+0x129): In function `smb_rq_new': /usr/src/sys/netsmb/smb_rq.c:121: undefined reference to `mb_done' smb_rq.o(.text+0x132):/usr/src/sys/netsmb/smb_rq.c:122: undefined reference to `md_done' smb_rq.o(.text+0x138):/usr/src/sys/netsmb/smb_rq.c:123: undefined reference to `mb_init' smb_rq.o(.text+0x154):/usr/src/sys/netsmb/smb_rq.c:126: undefined reference to `mb_put_mem' smb_rq.o(.text+0x15e):/usr/src/sys/netsmb/smb_rq.c:127: undefined reference to `mb_put_uint8' smb_rq.o(.text+0x166):/usr/src/sys/netsmb/smb_rq.c:128: undefined reference to `mb_put_uint32le' smb_rq.o(.text+0x17a):/usr/src/sys/netsmb/smb_rq.c:129: undefined reference to `mb_put_uint8' smb_rq.o(.text+0x1a6):/usr/src/sys/netsmb/smb_rq.c:135: undefined reference to `mb_put_uint16le' smb_rq.o(.text+0x1bd):/usr/src/sys/netsmb/smb_rq.c:137: undefined reference to `mb_put_mem' smb_rq.o(.text+0x1d4):/usr/src/sys/netsmb/smb_rq.c:140: undefined reference to `mb_put_uint16le' smb_rq.o(.text+0x1dc):/usr/src/sys/netsmb/smb_rq.c:141: undefined reference to `mb_reserve' smb_rq.o(.text+0x1e7):/usr/src/sys/netsmb/smb_rq.c:142: undefined reference to `mb_put_uint16le' smb_rq.o(.text+0x1f2):/usr/src/sys/netsmb/smb_rq.c:144: undefined reference to `mb_reserve' smb_rq.o(.text+0x1fd):/usr/src/sys/netsmb/smb_rq.c:145: undefined reference to `mb_put_uint16le' smb_rq.o(.text+0x205):/usr/src/sys/netsmb/smb_rq.c:146: undefined reference to `mb_reserve' smb_rq.o(.text+0x213):/usr/src/sys/netsmb/smb_rq.c:147: undefined reference to `mb_put_uint16le' smb_rq.o(.text+0x234): In function `smb_rq_done': /usr/src/sys/netsmb/smb_rq.c:154: undefined reference to `mb_done' smb_rq.o(.text+0x23d):/usr/src/sys/netsmb/smb_rq.c:155: undefined reference to `md_done' smb_rq.o(.text+0x422): In function `smb_rq_wstart': /usr/src/sys/netsmb/smb_rq.c:223: undefined reference to `mb_reserve' smb_rq.o(.text+0x496): In function `smb_rq_bstart': /usr/src/sys/netsmb/smb_rq.c:242: undefined reference to `mb_reserve' smb_rq.o(.text+0x645): In function `smb_rq_reply': /usr/src/sys/netsmb/smb_rq.c:338: undefined reference to `md_get_uint32' smb_rq.o(.text+0x65c):/usr/src/sys/netsmb/smb_rq.c:341: undefined reference to `md_get_uint8'
