Re: Corrected gettimeofday() test code
On Sat, 29 Nov 2003, Kris Kennaway wrote: * dmesg Attached ... * kernel configuration Attached ... * compiler options CFLAGS= -O -mpentium -pipe -g -DKVA_PAGES=512 COPTFLAGS= -O -mpentium -pipe -DKVA_PAGES=512 * time-related system configuration (whether ntpd/timed/ntpdate is running, and if so whether it's correcting for a seriously drifting clock) ntpdate running twice a day (11:59 23:59) * The kernel timecounter configuration, e.g. the kern.timecounter.method and kern.timecounter.hardware sysctls, and whether changing them has any effect. neptune# sysctl kern.timecounter kern.timecounter.method: 0 kern.timecounter.hardware: i8254 * The exact output of the corrected test program below (the original would give spurious errors if it didn't run at least once a second, which may have been confusing some people if their systems were sufficiently loaded). neptune# ./timetest 1070147310.273323 1070148005.799516 1070147310.273323 1070148005.799516 1070147313.623382 1070148009.299574 1070147313.623382 1070148009.299574 1070147320.223573 1070148015.699766 1070147320.223573 1070148015.699766 1070147351.373946 1070148046.800136 1070147351.373946 1070148046.800136 1070147361.174180 1070148056.700378 1070147361.174180 1070148056.700378 1070147374.524295 1070148070.100490 1070147374.524295 1070148070.100490 1070147378.674361 1070148074.100552 1070147378.674361 1070148074.100552 1070147396.124712 1070148091.700905 1070147396.124712 1070148091.700905 1070147413.724886 1070148109.401081 1070147413.724886 1070148109.401081 1070147447.925401 1070148143.401593 1070147447.925401 1070148143.401593 1070147450.475440 1070148146.101635 1070147450.475440 1070148146.101635 1070147453.175562 1070148148.701758 1070147453.175562 1070148148.701758 1070147474.275892 1070148169.702084 1070147474.275892 1070148169.702084 1070147527.826607 1070148223.302801 1070147527.826607 1070148223.302801 1070147531.876673 1070148227.302864 1070147531.876673 1070148227.302864 1070147531.876665 1070148227.402859 1070147531.876665 1070148227.402859 1070147545.176941 1070148240.703142 1070147545.176941 1070148240.703142 1070147616.077946 1070148311.504135 1070147616.077946 1070148311.504135 1070147616.178065 1070148311.704261 1070147616.178065 1070148311.704261 * The system status when the problem is observed (i.e. does it only occur under load; what else is running at the time) neptune# uptime 7:24PM up 47 days, 6:34, 5 users, load averages: 1.98, 1.23, 0.79 neptune# ps aux | wc -l 346 Anything else that I can provide, let me know ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 kernel.gz Description: Binary data dmesg.boot.gz Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Corrected gettimeofday() test code
On Sat, 29 Nov 2003, Don Bowman wrote: For this config (below), kern.timecounter.method=0 reproduces the problem, kern.timecounter.method=1 does not. Can anyone comment on what effect setting method to 1 has on the system? Like, would one notice a degradation in performance? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Time jumping on both 4.x and 5.x ...
In trying to isolate an issue where the PostgreSQL 'explain analyze' is
showing odd results (namely, negative time estimates on queries), Tom
Lane wrote a quick C program to test gettimeofday() (program attached) ...
the results on a 4.9-PRERELEASE kernel of Sep 20 14:16:48 ADT 2003 shows:
neptune# time ./timetest
out of order tv_sec: 1070068479 99040, prev 1070069174 725235
out of order tv_usec: 1070068479 99040, prev 1070069174 725235
out of order tv_sec: 1070069175 19687, prev 1070068479 99040
out of order tv_usec: 1070069175 19687, prev 1070068479 99040
out of order tv_sec: 1070068499 99377, prev 1070069194 625573
out of order tv_usec: 1070068499 99377, prev 1070069194 625573
out of order tv_sec: 1070069194 808542, prev 1070068499 99377
^C1.171u 23.461s 0:24.68 99.7% 5+169k 1+0io 0pf+0w
One person on the list has tried the same script on a 5.2 kernel, and
reports seeing similar results, but after a longer period of time (~30min)
...
In most (all?) cases, the offset appears to be ~+/-695 secs ... Linux ppl
on the list, running the same problem, seem to be able to reproduce the
issue, except they are only finding differences of 1 microsecond, and then
only on older kernels (2.2.x, apparently) ... those running newer Linux
kernels are reporting a clean run ...
Known problem?
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664#include stdio.h
#include sys/time.h
int
main()
{
struct timeval prevtime;
struct timeval curtime;
gettimeofday(prevtime, NULL);
for (;;)
{
gettimeofday(curtime, NULL);
if (curtime.tv_usec 0 || curtime.tv_usec = 100)
fprintf(stderr, bogus tv_usec: %ld %ld, prev %ld %ld\n,
(long int) curtime.tv_sec,
(long int) curtime.tv_usec,
(long int) prevtime.tv_sec,
(long int) prevtime.tv_usec);
if (curtime.tv_sec prevtime.tv_sec ||
curtime.tv_sec prevtime.tv_sec + 1)
fprintf(stderr, out of order tv_sec: %ld %ld, prev %ld %ld\n,
(long int) curtime.tv_sec,
(long int) curtime.tv_usec,
(long int) prevtime.tv_sec,
(long int) prevtime.tv_usec);
if (curtime.tv_usec prevtime.tv_usec
curtime.tv_sec != prevtime.tv_sec + 1)
fprintf(stderr, out of order tv_usec: %ld %ld, prev %ld
%ld\n,
(long int) curtime.tv_sec,
(long int) curtime.tv_usec,
(long int) prevtime.tv_sec,
(long int) prevtime.tv_usec);
prevtime = curtime;
}
return 0;
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time jumping on both 4.x and 5.x ...
On Fri, 28 Nov 2003, Kris Kennaway wrote: On Fri, Nov 28, 2003 at 09:32:30PM -0400, Marc G. Fournier wrote: In trying to isolate an issue where the PostgreSQL 'explain analyze' is showing odd results (namely, negative time estimates on queries), Tom Lane wrote a quick C program to test gettimeofday() (program attached) ... the results on a 4.9-PRERELEASE kernel of Sep 20 14:16:48 ADT 2003 shows: neptune# time ./timetest out of order tv_sec: 1070068479 99040, prev 1070069174 725235 out of order tv_usec: 1070068479 99040, prev 1070069174 725235 out of order tv_sec: 1070069175 19687, prev 1070068479 99040 out of order tv_usec: 1070069175 19687, prev 1070068479 99040 out of order tv_sec: 1070068499 99377, prev 1070069194 625573 out of order tv_usec: 1070068499 99377, prev 1070069194 625573 out of order tv_sec: 1070069194 808542, prev 1070068499 99377 ^C1.171u 23.461s 0:24.68 99.7% 5+169k 1+0io 0pf+0w One person on the list has tried the same script on a 5.2 kernel, and reports seeing similar results, but after a longer period of time (~30min) ... What hardware, kernel configuration, etc? Do you have a misconfigured ntpd/timed that is manually flapping the time around? Hardware for the above is a Dual-Xeon, 4Gig of RAM, and about 421 processes running on it currently ... kernel config is at the bottom, but I don't think there is anything 'abnormal' about it ... and note that I've had others be able to reproduce the problem on both 4.x and 5.x systems ... as to ntpd/timed ... don't run either ... run ntpdate twice a day (11:59 and 23:59), but that is it as far as playing with the clock is concerned ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 machine i386 cpu I686_CPU ident kernel maxusers0 makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols options NMBCLUSTERS=16384 options VM_KMEM_SIZE=(400*1024*1024) options VM_KMEM_SIZE_MAX=(400*1024*1024) options NULLFS #NULL filesystem options UNION #Union filesystem options NFS #Network File System options COMPAT_LINUX options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM options SHMMAXPGS=199608 options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) options SYSVSEM options SEMMNI=4096 options SEMMNS=8192 options SYSVMSG #SYSV-style message queues options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM#Rate limit bad replies options KBD_INSTALL_CDEV# install a CDEV entry in /dev options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa device pci device ahd # AHA39320/29320 and onboard AIC79xx devices options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. device scbus # SCSI bus (required) device da # Direct Access (disks) device pass# Passthrough device (direct SCSI access) device ses device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0at atkbdc? irq 12 device vga0at isa? pseudo-device splash device sc0 at isa? flags 0x100 device npx0at nexus? port IO_NPX irq 13 device em # Intel PRO/1000 adapter Gigabit Ethernet Card ( ``Wiseman'') pseudo-device loop# Network loopback pseudo-device ether # Ethernet support pseudo-device pty 256 # Pseudo-ttys (telnet etc) pseudo-device bpf #Berkeley packet filter options DDB options DDB_UNATTENDED options INCLUDE_CONFIG_FILE # Include this file in kernel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL
Re: Sound stop'd working after upgrade ...
On Wed, 26 Nov 2003, Melvyn Sopacua wrote: On Wednesday 26 November 2003 01:24, Marc G. Fournier wrote: pcm0: Intel ICH4 (82801DB) port 0xe400-0xe43f,0xe000-0xe0ff mem 0xe0102000-0xe01020ff,0xe0101000-0xe01011ff irq 17 at device 31.5 on pci0 pcm0: Avance Logic ALC650 AC97 Codec and, from what I can tell, the proper devices are being built in /dev, but try and play music using xmms, and I get nothing ... Not sure what to debug, or where ... help? :( Does 'mixer' report anything valid? I had this over the weekend and can't remember how I cured it (I think I cvsupped at the time), but I know that mixer gave some error instead of proper stats. nope, looks fine: ganymede# mixer Mixer vol is currently set to 75:75 Mixer pcm is currently set to 75:75 Mixer speaker is currently set to 88:88 Mixer line is currently set to 88:88 Mixer mic is currently set to 0:0 Mixer cd is currently set to 75:75 Mixer rec is currently set to 0:0 Mixer ogainis currently set to 50:50 Mixer line1is currently set to 75:75 Mixer phin is currently set to 0:0 Mixer phoutis currently set to 0:0 Mixer videois currently set to 75:75 Recording source: line is there some way of 'testing' it from the command line? I know you used to be able to cat a file to the device, but I think that was way back when it was one snd device instead of several ... I'm wondering if maybe the ich driver ... there was a problem introduced awhile back, that a cvsup and upgrade fixed ... just curious if maybe it got re-introduced, maybe ... ? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound stop'd working after upgrade ...
On Wed, 26 Nov 2003, Melvyn Sopacua wrote: On Wednesday 26 November 2003 01:24, Marc G. Fournier wrote: pcm0: Intel ICH4 (82801DB) port 0xe400-0xe43f,0xe000-0xe0ff mem 0xe0102000-0xe01020ff,0xe0101000-0xe01011ff irq 17 at device 31.5 on pci0 pcm0: Avance Logic ALC650 AC97 Codec and, from what I can tell, the proper devices are being built in /dev, but try and play music using xmms, and I get nothing ... Not sure what to debug, or where ... help? :( Does 'mixer' report anything valid? I had this over the weekend and can't remember how I cured it (I think I cvsupped at the time), but I know that mixer gave some error instead of proper stats. nope, looks fine: ganymede# mixer Mixer vol is currently set to 75:75 Mixer pcm is currently set to 75:75 Mixer speaker is currently set to 88:88 Mixer line is currently set to 88:88 Mixer mic is currently set to 0:0 Mixer cd is currently set to 75:75 Mixer rec is currently set to 0:0 Mixer ogainis currently set to 50:50 Mixer line1is currently set to 75:75 Mixer phin is currently set to 0:0 Mixer phoutis currently set to 0:0 Mixer videois currently set to 75:75 Recording source: line is there some way of 'testing' it from the command line? I know you used to be able to cat a file to the device, but I think that was way back when it was one snd device instead of several ... I'm wondering if maybe the ich driver ... there was a problem introduced awhile back, that a cvsup and upgrade fixed ... just curious if maybe it got re-introduced, maybe ... ? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound stop'd working after upgrade ...
On Wed, 26 Nov 2003, Melvyn Sopacua wrote: On Wednesday 26 November 2003 19:14, Marc G. Fournier wrote: On Wed, 26 Nov 2003, Melvyn Sopacua wrote: On Wednesday 26 November 2003 01:24, Marc G. Fournier wrote: pcm0: Intel ICH4 (82801DB) port 0xe400-0xe43f,0xe000-0xe0ff mem 0xe0102000-0xe01020ff,0xe0101000-0xe01011ff irq 17 at device 31.5 on pci0 pcm0: Avance Logic ALC650 AC97 Codec and, from what I can tell, the proper devices are being built in /dev, but try and play music using xmms, and I get nothing ... Not sure what to debug, or where ... help? :( Does 'mixer' report anything valid? I had this over the weekend and can't remember how I cured it (I think I cvsupped at the time), but I know that mixer gave some error instead of proper stats. nope, looks fine: [ ... ] is there some way of 'testing' it from the command line? I know you used to be able to cat a file to the device, but I think that was way back when it was one snd device instead of several ... * XMMS via esd and Arts running? * XMMS and null-output plugin? cdplay(1) and a cd is how I got onto the problem. portinstall ogg|mpg123 with an ogg/mp3 will also give you plenty of testing. There's wavplay also, but it needs proper wavheaders (ie: doesn't support raw wavs). I just disabled ACPI in my BIOs, and all works once more ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Sound stop'd working after upgrade ...
I upgraded my machine shortly after those changes with statfs ... upgrade went well, but sound stop'd working ... the device is being detected: pcm0: Intel ICH4 (82801DB) port 0xe400-0xe43f,0xe000-0xe0ff mem 0xe0102000-0xe01020ff,0xe0101000-0xe01011ff irq 17 at device 31.5 on pci0 pcm0: Avance Logic ALC650 AC97 Codec and, from what I can tell, the proper devices are being built in /dev, but try and play music using xmms, and I get nothing ... Not sure what to debug, or where ... help? :( Thanks ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sound no longer works ... ?
actually, just upgraded the machine and everything appears fine now ... what IRQ rerouting patch? ) On Sat, 25 Oct 2003 [EMAIL PROTECTED] wrote: Hiya I'm running: pcm0: NeoMagic 256AV mem 0xfea0-0xfeaf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0 pcm0: Asahi Kasei AK4542 AC97 Codec on a Sony VAIO ... Just wondering: had you applied the IRQ rerouting patch to get your sound working? I got caught out by this when I upgraded my VAIO and ended up getting mangled sound again. --Jon http://www.witchspace.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
sound no longer works ... ?
Just noticed that sound isnt' working on my laptop since my last upgrade (Oct 16), and one of our desktop's at the office is exhibiting the same thing ... Just CVSup new sources, and see nothing sound related having changed since my last one, so is this an isolated thing that nobody else is seeing? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sound no longer works ... ?
On Fri, 24 Oct 2003, Munish Chopra wrote: On 2003-10-24 23:39 -0300, Marc G. Fournier wrote: Just noticed that sound isnt' working on my laptop since my last upgrade (Oct 16), and one of our desktop's at the office is exhibiting the same thing ... Just CVSup new sources, and see nothing sound related having changed since my last one, so is this an isolated thing that nobody else is seeing? Sound's been working on all my builds, the latest one being from Oct 21. I've got a few SBxxx's, mainly Ensoniq chipsets. I'm running: pcm0: NeoMagic 256AV mem 0xfea0-0xfeaf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0 pcm0: Asahi Kasei AK4542 AC97 Codec on a Sony VAIO ... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Improvements to fsck performance in -current ...?
Due to an electrician flipping the wrong circuit breaker this morning, I had my servers go down hard ... they are all -STABLE, with one of the four taking a *very* long time to fsck: jupiter# ps aux | grep fsck root 361 99.0 2.3 95572 95508 p0 R+4:21PM 121:13.21 fsck -y /dev/da0s1h jupiter# date Tue Sep 30 18:37:02 ADT 2003 jupiter# Now, CPU time is rising, so I figure its still working away, and fsck shows: jupiter# fsck -y /dev/da0s1h ** /dev/da0s1h ** Last Mounted on /vm ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts so it isn't finding any errors ... A friend of mine asked if we had a journalling file system, which I told him know, as I don't believe we do ... but are/have there been any improvements to fsck in -CURRENT to improve performance on large file systems (this is a 6x36G RAID5 system)? Does UFS2 address any of this? I've actually had a 6x18gig RAID5 file system once take 11+hrs to fsck ... and when it was completed, everything seemed fine, with no reports of any file or directory corruption ... it obviously did a good job of checking the file system, just hate the lengthy downtime ... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Improvements to fsck performance in -current ...?
On Tue, 30 Sep 2003, Kevin Oberman wrote: Current has two major changes re speeding up fsck. The most significant is the background operation of fsck on file system with soft updates enabled. Because of the way softupdates works, you are assured of metadata consistency on reboot, so the file systems can be mounted and used immediately with fsck started up in the background about a minute after the system comes up. Actually, I had this blow up on my -CURRENT desktop once ... didn't have a clue on how to debug it, so I switched from fsck -p to fsck -y to prevent it from happening again :( Now,I don't/wouldn't have softupdates enabled on / .. does the 'background fsck' know to not background if softupdates are not enabled? I'm going to switch back to -p and look a bit closer the next time it happens (if it happens) to see if it is/was a softupdate file system that failed, now that I have a better idea of what I'm looking for ... I suspect that these enhancements may both require that soft updates be enabled for the file systems. are either of these enhancements back-patchable to the 4.x fsck, or do they require some non-4.x compatible changes to work? ... I'm at 3.5hrs and counting right now ... any speedup would be great ... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Improvements to fsck performance in -current ...?
On Wed, 1 Oct 2003, Lukas Ertl wrote: are either of these enhancements back-patchable to the 4.x fsck, or do they require some non-4.x compatible changes to work? It's not just the fsck application itself, background fsck basically needs file system snapshots, which are only available on UFS2, and I'm not sure if they can be backported to UFS1 at all. Ah, okay, so when I move my servers to 5.x, then I'm going to need to reformat the systems from scratch, else I lose some serious improvements ... is there a list somewhere of what UFS2 has over UFS1? file system snapshots, is that similar to journalling? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: -current brake ufs for -stable
On Sun, 21 Sep 2003, Doug White wrote: On Sun, 21 Sep 2003, Sergey Matveychuk wrote: I've installed both -current and -stable on my box. One of partition I plan to share betwen them (place ports/distfiles there). I newfs'ed it from -stable and wrote on it from -current. When I booted with -stable I've found the partition FS was broken. I think it's because of extended atributes -current wrote on it. I don't like to turn off extended attributes on -current at all. I'd like to have some option for mount to disable it (I've not found it on manpage). If you newfs'd the partition with -current, you made it UFS2. -stable can't mount UFS2 partitions. Newfs it with -stable (or the appropirate option on -current, I don't recall it) so its mountable on both systems. Actually, he did state that I newfs'ed it from -stable and wrote on it from -current ... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: se7500+dual xeon?
On Thu, 6 Feb 2003, John Baldwin wrote: His board is a WV2, not a CW2. The WV2's should work fine though they might need a BIOS update. I can verify the WV2's ... just built a server with one of these .. can't verify the BIOS issue, as it was upgraded before I got the machine, but have been most impressd with both the server and the chassis ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
make release fails building floppies ...
I'm slowly getting closer, but am not quite there yet :( I'm at the stage where its building teh floppies, but its telling me that the md devices are out of disk space: if [ -d /R/stage/driversfd ]; then sh -e /usr/local/5.0/src/release/scripts/doFS.sh /R/stage/floppies/drivers.flp /R/stage /mnt 1440 /R/stage/driversfd 4 fd1440; cd /R/stage/driversfd awk -f /usr/local/5.0/src/release/scripts/driver-desc.awk *.dsc /R/stage/floppies/DRIVERS.TXT; fi /dev/md3c: 1.4MB (2880 sectors) block size 4096, fragment size 512 using 2 cylinder groups of 1.22MB, 312 blks, 32 inodes. super-block backups (for fsck -b #) at: 32, 2528 1871 blocks Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/md3c 1391 987 40471% 3329 53% /mnt *** Filesystem is 1440 K, 404 left *** 4 bytes/inode, 29 left sh -e /usr/local/5.0/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 4320 /R/stage/mfsfd 8000 minimum3 /dev/md3c: 4.2MB (8640 sectors) block size 4096, fragment size 512 using 4 cylinder groups of 1.06MB, 271 blks, 160 inodes. super-block backups (for fsck -b #) at: 32, 2200, 4368, 6536 6496 blocks Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/md3c 4175 3309 86679% 96 542 15% /mnt *** Filesystem is 4320 K, 866 left *** 8000 bytes/inode, 542 left mfsroot: 67.4% /dev/md3c: 1.4MB (2880 sectors) block size 4096, fragment size 512 using 1 cylinder groups of 1.41MB, 360 blks, 32 inodes. super-block backups (for fsck -b #) at: 32 /mnt: write failed, filesystem is full cp: /mnt/mfsroot.gz: No space left on device *** Error code 1 I ran 'make release' as: make relesae \ CHROOTDIR=/usr/local/release \ BUILDNAME=vaio \ [EMAIL PROTECTED]:/home/ncvs \ RELEASETAG=RELENG_5_0 \ NODOC=YES \ KERNEL_FLAGS=-j 5 \ NOPORTS=YES \ WORLD_FLAGS=-j 5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make release fails building floppies ...
got it ... figured out how the mfsfd/modules is generated, and just trim'd down the driver.conf file to the bare essentials ... On Thu, 23 Jan 2003, Juli Mallett wrote: * De: Marc G. Fournier [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: make release fails building floppies ... ] I'm slowly getting closer, but am not quite there yet :( I'm at the stage where its building teh floppies, but its telling me that the md devices are out of disk space: This is probably my fault, since tunefs(8) needs libufs now. Converting other things that could use it that are on the floppies to use libufs would be a start. My newfs changes might be enough. -- Juli Mallett [EMAIL PROTECTED] AIM: BSDFlata -- IRC: juli on EFnet. OpenDarwin, Mono, FreeBSD Developer. ircd-hybrid Developer, EFnet addict. FreeBSD on MIPS-Anything on FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Simple way to build boot disks?
G'day ... I'm having a bugger of a time getting my laptop with a third-party ethernet adapter installed with 5.0, since it won't properly configure the adapter ... what I'd like to do is build a custom boot kernel, that gets rid of everything but what I require for that laptop, so that the onboard doesn't conflict with the 3rd party one ... all I can find so far on how to do this is to go through the whole 'make release' procedure ... is there an easier way of doing this that I'm not finding? thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
make release.9 fails ... ?
Evening ... I found the release man page this evening, after more searching, and understand from it that a simple: cd /usr/src make buildworld cd release make floppies Should give me what I need ... But, when I try, the release.9 stage gives: atelier# make release.9 rm -rf /R/stage/mfsfd mkdir /R/stage/mfsfd cd /R/stage/mfsfd mkdir -p etc/defaults dev mnt stand/etc/defaults stand/help ( cd /R/stage/mfsfd for dir in bin sbin ; do ln -sf /stand $dir; done ) cp /R/stage/trees/base/sbin/dhclient-script /R/stage/mfsfd/stand cp: /R/stage/trees/base/sbin/dhclient-script: No such file or directory *** Error code 1 Known bug, or is there another step that I need to run first? Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: I'm leaving the project
On Tue, 17 Dec 2002, Matthew Dillon wrote: : :Matt Dillon wrote: : Thanks to my dear friend Warner Losh. I've decided to leave FreeBSD and : flame in another project. Maybe I could join OpenBSD, the seem to share : my views on how to deal with other people. : : I hereby give maintainership of all my code to Warner, or, whoever wants : it, for that matter. : :Does anyone know why this person is trying to (poorly) impersonate MD? Probably because I lambast him mercilessly for being such a whimp. It's kinda sad, actually. He's probably not making any friends with the people running the blind proxies he abuses to post, either. -Matt Matthew Dillon [EMAIL PROTECTED] God, now this thread gave me a panic (and a heartattack) ... its funny how many times you can read someone's posts, and see their writing style, and still be sucker-punched:) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Installing 5.0-RC1 on Sony Vaio z505s with Linksys Combo Card ...
Is there anyway of doing this? the boot disk is recognizing the card, but is followed by: device_probe_and_attach: ed1 attach returned 6 My first guess is that its conflicting with the existing fxp0 device that was detected before it, since its sharing the IRQ, but dont' know how to debug whether that is it or not ... Help? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: snd_pcm module not usable ... ?
perfect, thanks ... worked like a charm ... On Mon, 25 Nov 2002, Daniel C. Sobral wrote: Marc G. Fournier wrote: Maybe i'm missing something that i need to load, but I took the pcm device out of my kernel config, figuring that I could use the snd_pcm module ... loaded it, but still can't seem to get sound? is there something else I need to do with devfs for this, or do Ihave to compile in the pcm device? pcm is the front-end. You need the back-end, the actual sound driver. Try snd_driver_load=YES. It ought to load everything. Or you can kldload it from the command line, and then check /var/log/messages to find out which driver you are supposed to use. On loader, loading any sound driver will bring in snd_pcm automatically, as a dependency. -- Daniel C. Sobral (8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Fundamentalist Debianites, core children of the Linuxen sounds like it could come from the Book of Mormon, or Tolkien on a bad day... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
compiling kdebase3 under -CURRENT of Nov 26th fails ...
`/usr/local/ports/usr/ports/x11/kdebase3/work/kdebase-3.0.3' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/x11/kdebase3. *** Error code 1 Stop in /usr/ports/x11/kde3. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall3489.0 make ** Fix the problem and try again. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! x11/kde3 (linker error) Marc G. Fournier [EMAIL PROTECTED] Senior Systems AdministratorAcadia University These are my opinions, which are not necessarily shared by my employer To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: compiling kdebase3 under -CURRENT of Nov 26th fails ...
On Mon, 25 Nov 2002, Kris Kennaway wrote: On Mon, Nov 25, 2002 at 12:11:44PM -0400, Marc G. Fournier wrote: I just CVSup'd and rebuilt (and installed) world/kernel, just in case it was a transient error from last week ... but same error. I know zero about C++, but what little I know, aren't the 'undefined references' standard C++ functions? *raised eyebrows* Do you have stale headers in /usr/include? Never thought of that one ... just cleaned them out and am re-trying again, thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
snd_pcm module not usable ... ?
Maybe i'm missing something that i need to load, but I took the pcm device out of my kernel config, figuring that I could use the snd_pcm module ... loaded it, but still can't seem to get sound? is there something else I need to do with devfs for this, or do Ihave to compile in the pcm device? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Problems Loading DP2 via FTP through de driver ...
I've been running 4.x on my desktop for months now, with the de driver ... I've decided that since we're coming up on release, let's move up to it (yes, I know, its not perfect yet, but its only my desktop) ... First problem I hit was that my ethernet card wasn't detected ... from ftp'ng down the original files, I figured that the driver for it must be on the drivers.flp, but I couldn't find anywhere that detailed how to make use of it ... I finally figured out how to do it, after much trial-n-error, but could someone maybe document this in the README.txt file, or maybe have a 'Press [Space] to loaddriver from drivers.flp' message into the boot routine? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Problems with DP2 install floppies ... ?
Just got everything up, made sure that it knew how to mount my file systems, watched it fsck those same file systems ... but as soon as it started to install, it reported out of space errors ... On ALT-F2, it looks like its trying to write to: ./usr/share/dict/.. instead of, what I believe its supposed to be: /mnt/usr/share/dict/.. which would explain why its running out of disk space, as its trying to write to the floppy ... ? Going to ALT-F4 and doing a df shows that everything appears to be mounted as expected (/mnt, /mnt/dev, /mnt/usr, etc) ... known problem, or did I screw up a step here? thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problems with DP2 install floppies ... ?
'K, that is what I did ... One final issue on this first attempt ... when I go into 'partition' an existing drive, how do I get it to 'mount' my existing swap device? rightnow, I just deleted and created it, but that just doesn't sound ... safe ... On Tue, 19 Nov 2002, John Baldwin wrote: On 19-Nov-2002 Marc G. Fournier wrote: Just got everything up, made sure that it knew how to mount my file systems, watched it fsck those same file systems ... but as soon as it started to install, it reported out of space errors ... On ALT-F2, it looks like its trying to write to: ./usr/share/dict/.. instead of, what I believe its supposed to be: /mnt/usr/share/dict/.. which would explain why its running out of disk space, as its trying to write to the floppy ... ? Going to ALT-F4 and doing a df shows that everything appears to be mounted as expected (/mnt, /mnt/dev, /mnt/usr, etc) ... known problem, or did I screw up a step here? thanks ... Did you try to restart your install via Ctrl-C? If so, don't, the restart stuff doesn't really work right. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Installing DP2 onto Sony VAIO with Linksys Ethernet Card ...
Evening all ... Working on getting DP2 installed on my Sony VAIO ... the fxp0 onboard, I don't have the adapter for anymore (wires frayed), so I have a Linksys Combo EthernetCard plugged into the PCMCIA slot ... Booted up off of floppy, and looking at ALT-F2, it has detected the ethernet card, but its followed by: device_probe_and_attach: ed1 attach returned 6 And isn't offered as an option when trying to configure the network ... From /usr/include/errno.h, 6 is 'Device not configured' ... Now, looking further up the screen, the fxp0 ethernet is also using irq 9, so I don't know if this is an IRQ conflict or something? I thought about disabling the fxp driver, but that option is no longer available that I can see ... ? Is there something else I should be doing? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
NEWCARD support with Linksys card on Sony VAIO ...
Morning all ... I'm finally trying to get my laptop back up and running using -CURRENT ... back on August 16th, I did an upgrade that totally hosed the ability to use my ethernet, and due to the way that I erroneously did the upgrade, I can't go back to the old kernel :( I've searched the archives, and find others that have had the problem, but haven't found a fix as of yet ... is there something in the kernel sources that I can change to get the kernel to see the ethernet device, so taht I can upgrade my kernel to the latest? A value/flag that needs to be set? As to the old kernel, I did an 'installworld', so when I try and ifconfig the device, I'm getting an etheraddress of 00:00:00:00:00, altho it is detecting a card, so its pretty useless :( Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
NEWCARD support for Linksys Ethernet broken?
Just upgraded my laptop to the latest -CURRENT ... everything boots fine, but my ethernet no longer exists (it worked great on my June 6th kernel) ... I'm using NEWCARD support in the kernel, and if_ed is loaded according to kldstat ... I've searched Google, and nadda there ... known problem, or am I missing something that has changed? Just re-checked UPGRADING and nothing in there about it either ... Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Sun, 23 Jun 2002, Martin Blapp wrote: Very very strange ... How recent is your CURRENT ? Mine is : FreeBSD 5.0-CURRENT #2: Fri May 31 09:49:38 CEST 2002 root@fuchur:/usr/ports/x11/XFree86-4-libraries# pwd /usr/ports/x11/XFree86-4-libraries root@fuchur:/usr/ports/x11/XFree86-4-libraries# cc --version gcc (GCC) 3.1.1 20020617 (prerelease) [FreeBSD] make (using cc -c -O -pipe -O2 -ansi -pedantic), I removed files/patch-d [...] Sun Jun 23 16:05:30 CEST 2002 build of X Window System complete. Here it also worked with the last gcc snapshot. My experiences here are that building X works, installing X dooesn't ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
More X breakage in XFree86-4-Servers ...
BRARY_PATH=../../../../exports/lib cc -c -O -pipe -D_OLD_STDIO -ansi -pedantic
-Dasm=__asm -Wall -Wpointer-arith -I../../../../exports/include
-I../../../../exports/include/X11 -I../../../../include/extensions
-I../../../../extras/Mesa/src -I../../../../lib/GL/dri -I../../../..
-I../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS
-DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI
-DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA-DUSE_X86_ASM
-DUSE_MMX_ASM -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith
-I../../../../exports/include -I../../../../exports/include/X11
-I../../../../include/extensions -I../../../../extras/Mesa/src
-I../../../../lib/GL/dri -I../../../.. -I../../../../exports/include -DCSRG_BASED
-DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI
-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_REND
ERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -DUSE_X86_ASM -DUSE_MMX_ASM-fPIC
translate.c
In file included from translate.c:779:
../../../../extras/Mesa/src/trans_tmp.h: In function `trans_1_GLdouble_1ub_elt':
../../../../extras/Mesa/src/trans_tmp.h:124: could not find a spill register
(insn 96 94 97 (set (subreg:SF (reg:QI 75) 0)
(plus:SF (reg:SF 8 st(0) [76])
(reg:SF 9 st(1) [80]))) 525 {*fop_sf_comm_nosse} (insn_list 87 (nil))
(expr_list:REG_DEAD (reg:SF 8 st(0) [76])
(nil)))
../../../../extras/Mesa/src/trans_tmp.h:124: Internal compiler error in failed_reload,
at reload1.c:5050
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
*** Error code 1
Stop in
/usr/local/ports/usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/GL/mesa/src.
*** Error code 1
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Tue, 4 Jun 2002, Stanislav Grozev wrote: On Tue, Jun 04, 2002 at 07:08:32AM -0500, Michael D. Harnois wrote: #pragma weak foo = bar with either #pragma weak foo = bar /* this is easier */ snip/ I tried the quotation mark fix, and all it does is change the error message to UIThrStubs.c:102: warning: malformed #pragma weak, ignored snip/ which doesn't really seem to be a solution. are you sure that you're with the right gcc? mine compiles this fine. but regardless which one I use (__attribute__ or the quotation), later on the process i get the internal compiler error in Mesa. not that I think the two are related, though. I tried here too, latest GCC in 5.0-CURRENT from this weekend, and get the same 'ignored' stuff, after which it does continue onto the Mesa where it does fail ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
stupid question, but what is the fix for the #pragma weak issue? :(
On Mon, 3 Jun 2002, Stanislav Grozev wrote:
Hello,
I have a -CURRENT system (world from yesterday, ports from today).
I'm trying to compile the XFree86-libraries-4.2.0 from ports, but
I have troubles. After resolving the one with the #pragma weak,
and also one with a missing ../ from one of the Mesa Makefiles,
now I get the following:
-
LD_LIBRARY_PATH=../../../../../exports/lib cc -c -O -pipe -Wp,-w -march=pentium
-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith
-I../../../../../exports/include/X11 -I../../../../../include/extensions
-I../../../../../extras/Mesa/src/OSmesa -I../../../../../extras/Mesa/src
-I../../../../../extras/Mesa/include -I../../../../..
-I../../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO
-DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL
-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith
-I../../../../../exports/include/X11 -I../../../../../include/extensions
-I../../../../../extras/Mesa/src/OSmesa -I../../../../../extras/Mesa/src
-I../../../../../extras/Mesa/include -I../../../../..
-I../../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO
-DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL
-fPIC ../../../../../lib/GL/mesa/src/translate.c
In file included from ../../../../../lib/GL/mesa/src/translate.c:779:
../../../../../extras/Mesa/src/trans_tmp.h: In function `trans_1_GLdouble_1ub_elt':
../../../../../extras/Mesa/src/trans_tmp.h:124: could not find a spill register
(insn 96 94 97 (set (subreg:SF (reg:QI 75) 0)
(plus:SF (reg:SF 8 st(0) [76])
(reg:SF 9 st(1) [80]))) 525 {*fop_sf_comm_nosse} (insn_list 87
(nil))
(expr_list:REG_DEAD (reg:SF 8 st(0) [76])
(nil)))
../../../../../extras/Mesa/src/trans_tmp.h:124: Internal compiler error in
failed_reload, at reload1.c:5050
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
*** Error code 1
Stop in /home/scratch/ports/x11/XFree86-4-libraries/work/xc/lib/GL/mesa/src/OSmesa.
logrus#
-
I don't have any idea what to do to fix it. Any help would be appreciated.
If any further info, or details, or testing are needed, I'll be glad
to provide it. Thanks.
-tacho
--
[a lie is my shield] | [http://daemonz.org/ || [EMAIL PROTECTED]]
0x44fc3339 || [02b5 798b 4bd1 97fb f8db 72e4 dca4 be03 44fc 3339]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: State of the ports collection
Terry, I have a high speed connection over here, so if its purely a 'typing' change sort of thing, if you want to tell me what needs to be done to fix these, I can make the changes and submit patches (I can't login to my FreeBSD account to make the commits myself ... my key went out of date *sigh*) ... On Mon, 3 Jun 2002, Kris Kennaway wrote: On Mon, Jun 03, 2002 at 04:54:32PM -0700, Terry Lambert wrote: Kris Kennaway wrote: But the error handling path of any program is not one of them; if you are optimizing something other than the success path, there is something fundamentally wrong with your program or problem statement. So how about you do more than the average person's part towards reducing the amount of evil in the world, by fixing broken ports and submitting patches. I can give you a list of the broken ports. I have a slow link. As long as the ports aren't the size of Mozilla, I would be willing to use my slow link to hack some of them to not directly reference the error lists from libc. Thanks, that would be great. Here's the sys_nerr list so far: NeTraMet-4.3.log:../../src/bgp/integrat/readbgp.c:118: conflicting types for `sys_nerr' arm-aout-gcc295-2.95.3.log:strerror.c:465: conflicting types for `sys_nerr' arm-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: conflicting types for `sys_nerr' avr-binutils-2.11.log:strerror.c:468: conflicting types for `sys_nerr' bc-gcc-2.7.2p1.0.2.log:gcc.c:178: conflicting types for `sys_nerr' bogosort-0.3.3.log:error.c:126: conflicting types for `sys_nerr' cap-6.0.198.log:ablog.c:94: conflicting types for `sys_nerr' coco-2.3.log:emacs.c:514: conflicting types for `sys_nerr' cwish-3.52.log:header.c:121: conflicting types for `sys_nerr' dlx-2.0.log:sim.c:2835: conflicting types for `sys_nerr' dviselect-1.3.log:error.c:36: conflicting types for `sys_nerr' egcs-1.1.2.log:strerror.c:465: conflicting types for `sys_nerr' gcc-2.7.2.3.log:gcc.c:182: conflicting types for `sys_nerr' gup-0.4.log:rfc822.h:247: conflicting types for `sys_nerr' harvest-1.5.log:print.c:80: conflicting types for `sys_nerr' i386-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: conflicting types for `sys_nerr' i960-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: conflicting types for `sys_nerr' ja-okphone-1.2.log:misc.c:34: conflicting types for `sys_nerr' ko-hanemacs-19.34b.1.log:emacs.c:434: conflicting types for `sys_nerr' m3gdb-4.17.log:/tmp/a/ports/lang/m3gdb/work/m3gdb-4.17/src/contrib/binutils/libiberty/strerror.c:465: conflicting types for `sys_nerr' m6811-binutils-2.10.log:strerror.c:465: conflicting types for `sys_nerr' m68k-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: conflicting types for `sys_nerr' mgetty-1.1.28.01.10.log:logfile.c:55: conflicting types for `sys_nerr' mips-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: conflicting types for `sys_nerr' mipsel-linux-binutils-2.10.91.log:strerror.c:468: conflicting types for `sys_nerr' objprelink-1.0_2.log:strerror.c:468: conflicting types for `sys_nerr' pgcc-2.95.2.1.log:strerror.c:465: conflicting types for `sys_nerr' powerpc-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: conflicting types for `sys_nerr' sdcc-2.1.9.log:cpplib.c:7451: conflicting types for `sys_nerr' sdcc-2.1.9.log:cpplib.c:7451: conflicting types for `sys_nerr' sh-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: conflicting types for `sys_nerr' sparc-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: conflicting types for `sys_nerr' squid-2.4_9.log:util.c:79: conflicting types for `sys_nerr' tintin-1.5.9.log:utils.c:60: conflicting types for `sys_nerr' zh-tintin-1.5.9.log:utils.c:60: conflicting types for `sys_nerr' There are others hidden by dependencies that fail to build. This is an exercise that's more about typing speed than thinking, anyway. For the most part, yeah. There are probably some tricky ones. For example, some of the stdio breakage is difficult to fix. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
has any of this been reported to the XFree86 folk? I just CVSup'd the latest XFree86 source code and this #pragma condition appears to still exist :( On Mon, 3 Jun 2002, Stanislav Grozev wrote: On Mon, Jun 03, 2002 at 11:44:43AM -0300, Marc G. Fournier wrote: stupid question, but what is the fix for the #pragma weak issue? :( you replace #pragma weak foo = bar with either #pragma weak foo = bar /* this is easier */ or if __GNUC__ = 3 int foo() __attribute__ ((weak, alias (bar))); #endif /* __GNUC__ */ . :-) but that only gets you to the Mesa mess;-( -tacho To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
fts_read errors ... what causes?
I get this semi-randomly on my laptop when doing a delete ... softupdates are enabled on the file system in question, and am running -CURRENT as of last night, if any of that matters? === Cleaning for XFree86-font75dpi-4.2.0 rm: fts_read: No such file or directory *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
XFree86-4-libraries compile fails in UIThrStubs.c ... GCC 3.1 issue?
I'm running 5.0-CURRENT, with gcc 3.1: mobile# gcc -v Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.1 [FreeBSD] 20020509 (prerelease) Is this an issue with GCC 3.1, or something else I'm not thinking of ... ? -- Line102: #pragma weak pthread_self = _Xthr_self_stub_ rm -f UIThrStubs.o LD_LIBRARY_PATH=../../exports/lib cc -c -O -pipe -D_OLD_STDIO -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI -DMALLOC_0_RETURNS_NULL-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -fPIC UIThrStubs.c UIThrStubs.c:102: alias arg not a string UIThrStubs.c:103: alias arg not a string UIThrStubs.c:104: alias arg not a string UIThrStubs.c:105: alias arg not a string UIThrStubs.c:106: alias arg not a string UIThrStubs.c:107: alias arg not a string UIThrStubs.c:108: alias arg not a string UIThrStubs.c:109: alias arg not a string UIThrStubs.c:110: alias arg not a string UIThrStubs.c:111: alias arg not a string UIThrStubs.c:113: alias arg not a string UIThrStubs.c:114: alias arg not a string UIThrStubs.c:115: alias arg not a string UIThrStubs.c:131: warning: `_Xthr_self_stub_' defined but not used UIThrStubs.c:139: warning: `_Xthr_zero_stub_' defined but not used *** Error code 1 Stop in /usr/local/ports/usr/ports/x11/XFree86-4-libraries/work/xc/lib/XThrStub. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Undefined symbol SYS_uuidgen?
Cool, just did a reinstall of the include files and things appear to be working much better now ... thanks :) On Sat, 1 Jun 2002, Terry Lambert wrote: Dan Nelson wrote: In the last episode (Jun 01), Marc G. Fournier said: Performed a 'make buildworld' successfully, but as soon as I tried the 'installworld', when its trying to do the install of libc.so.5, it gives an error to the effect of: /usr/libexec/ld-elf.so.1: /usr/lib/libc.so.5: Undefined symbol SYS_uuidgen Sounds like your kernel and userland are out of synch. Try installing a new kernel, and rerunning installworld. You may need to build the kernel on another machine if you can't roll back your libc. It's always a good idea to back up libc before a world build :) Undefined symbol, not Undefined system call. Sounds more like the sys include files were not installed before the libc was built, since there's a silly script that translates /usr/include/sys/syscall.h to stubs. Another possibility is that the Makefile's in the /usr/src/lib/libc hierarchy need updating. Generally, I'd expect the libc.so version number to bump before seeing this problem, anyway. 8-(. Looks like someone failed to bump a version number. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Sony Vaio, LinkSys EC2T 5.0-CURRENT ...
On Sat, 1 Jun 2002, Ollivier Robert wrote: According to Marc G. Fournier: If I run 'pccardd -f /etc/defaults/pccard.conf' from the command line, it comes back that its matched the card, followed by a line that states: Try running NEWCARD instead. I had some probmem a while ago with my Z600TEK and moving to NEWCARD fixed it. D'oh ... I had thought, for some reason, that NEWCARD was the default :( Just redid my kernel with NEWCARD, and now my Surecom EP-428X works too ... woo hoo ;) Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
getcwd() failed ...
I'm getting the following randomly while trying to do a 'make buildworld' ... library problem? Or something else that I'm not seeing? === gnu/lib/libstdc++ === gnu/lib/libstdc++/doc cd: getcwd() failed: No such file or directory *** Error code 2 Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Sony Vaio, LinkSys EC2T 5.0-CURRENT ...
Morning all ... After getting nowhere with the Surecom EP-428X that I picked up, I went out today and grabbed one of the Linksys EC2T, figuring it's on the list of supported devices I found, and I think I'm s close ... First, I'm running a VAIO PCG-Z505S ... I've upgraded to 5.0-CURRENT as of May 21st, mainly due to the Surecom, but figure I'll stay there for the Linksys ... If I run 'pccardd -f /etc/defaults/pccard.conf' from the command line, it comes back that its matched the card, followed by a line that states: 'driver allocation failed for Linksys(...): Inappropriate ioctl for device' According to dmesg, I have: pcic0: Ricoh RL5C475 PCI-Cardbus Bridge irq 9 at device 10.0 on pci0 pcic0: PCI Memory allocated: 0x4400 pccard0: PC Card bus (classic) on pcic0 If I pull out the card, the machine itself hangs ... and searching on Google, it talks about pccard + shared interrupts ... and on this, the internal ethernet (fxp0) is using irq 9 and the USB controller (uhci0) is using irq 9 ... I looked in the pcic man page, and found the references to hw.pcic.irq, which mine is set to 0 ... and hw.pcic.intr_path, which mine is set to 2 ... it talks about being able to switch to ISA interrupt by changing intr_path to 1, which I tried, with an .irq setting of 10 ... still hung, so that wasn't the right direction ... So, I'm pretty much at an impasse right now as to what to try next ... does anyone have an experiences with this combination and/or suggestions on what to try next ... ? Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Surecom EP-428X PCCARD in -CURRENT
Morning all ... Just got my Vaio Z505s upgraded to -CURRENT, in order to get my new Surecom Ethernet PCMCIA card to work ... looked in /etc/defaults/pccard.conf, and found the EP-427X card(s) in there, but haven't got a clue on how to setup a similar entry for the -428X to be recognized ... Pointers/directions? Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Apache + threads under FreeBSD ...
I'm looking at getting a threaded Apache working under FreeBSD-STABLE (as of this past weekend) ... if I start up the server and connect with a browser, it doesn't send anything back, *except* if I kill the apache server right after the connection ... I've checked with the Apache folk, and someone pointed me to the STATUS file, where I found: * Generate a good bug report to send to the FreeBSD hackers that details the problems we have seen with threads and system calls (specifically sendfile data is corrupted). From our analysis so far, we don't think that this is an APR issue, but rather a FreeBSD kernel issue. Our current solution is to just disable threads across the board on FreeBSD. MsgID: [EMAIL PROTECTED] Status: Fixed in -CURRENT. MFC in about a week. Continuing testing with threads on FreeBSD. FreeBSD PR kern/32684: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/32684 == Reading the PR, alfred put a fix in place shortly after (~mid December of 2001), but I'm wondering if anyone knows whether this was migrated back down to -STABLE, and, if not, what would be involved to have that done? Is it a fix that *can* be MFCd? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Apache + threads under FreeBSD ...
A little more digging in the CVS logs, it looks like it was, in fact, MFCs to 4.x: revision 1.2.2.3 date: 2001/12/15 20:03:52; author: alfred; state: Exp; lines: +51 -5 MFC: 1.6 sendfile wrap fix. but, in January, things were reverted in 5.x, but never reflected in 4.x? revision 1.7 date: 2002/01/22 23:35:09; author: dg; state: Exp; lines: +0 -11 Undo the work-around for the sendfile bug where nbytes needed the hdr/trl size added to it in order for it to work properly when nbytes != 0. Reviewed by:alfred MFC after: 3 days On Tue, 21 May 2002, Marc G. Fournier wrote: I'm looking at getting a threaded Apache working under FreeBSD-STABLE (as of this past weekend) ... if I start up the server and connect with a browser, it doesn't send anything back, *except* if I kill the apache server right after the connection ... I've checked with the Apache folk, and someone pointed me to the STATUS file, where I found: * Generate a good bug report to send to the FreeBSD hackers that details the problems we have seen with threads and system calls (specifically sendfile data is corrupted). From our analysis so far, we don't think that this is an APR issue, but rather a FreeBSD kernel issue. Our current solution is to just disable threads across the board on FreeBSD. MsgID: [EMAIL PROTECTED] Status: Fixed in -CURRENT. MFC in about a week. Continuing testing with threads on FreeBSD. FreeBSD PR kern/32684: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/32684 == Reading the PR, alfred put a fix in place shortly after (~mid December of 2001), but I'm wondering if anyone knows whether this was migrated back down to -STABLE, and, if not, what would be involved to have that done? Is it a fix that *can* be MFCd? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: How to dump a 4gig system on panic ?
Well, I have a machine to debug/test this on, if you can provide some directions on how to debug and get her up to date? :) With the larger and larger systems that ppl are implementing, is this something that might be useful to get into the core system? On Sat, 18 May 2002, Andrew Gallatin wrote: Marc G. Fournier writes: Okay, seem to be about halfway there ... client kldload's no problem, server runs ... do a ctl-alt-esc to get into DDB and type panic, and it gives a message that its looking for the server and it finds it on the right IP ... then it prints out a '1023' and finishes the panic ... On the 'dump server', a vmcore gets created, but its zero length ... thoughts? As I said, it hasn't been used for quite some time. It may require work to get it working again. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: How to dump a 4gig system on panic ?
Oh, I like the netdump one ... I have a machine sitting right beside this one that I can use to dump to ... has anyone thought to include this as a 'standard' sort of thing with FreeBSD? So that it keeps up with the current code? On Fri, 17 May 2002, Andrew Gallatin wrote: There are 3 things you could do: a) Limit your memory size in the loader b) Use partial dumps c) Use network dumps if you have another machine to run the dump server on. Both the netdump partial dump code can be found at: http://www.cs.duke.edu/~anderson/freebsd/ Both may be a little out of date require some work to get working with a recent -stable, as they were developed in the days when 4.0 was -current. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: How to dump a 4gig system on panic ?
Well, downloaded the files (a .tar.gz would be nice? *grin*) and the client built perfectly, and kldload worked fine ... is there some way someone can suggest of 'simulating a crash'? Some way to test to make sure that it is working as expected? I have a 4.6-PRE machine on my desk that I'd like to test with before I try it on the real thing, if at all possible? On Fri, 17 May 2002, Andrew Gallatin wrote: Marc G. Fournier writes: Oh, I like the netdump one ... I have a machine sitting right beside this one that I can use to dump to ... has anyone thought to include this as a 'standard' sort of thing with FreeBSD? So that it keeps up with the current code? I plan to integrate partial dumps as an option at some point, but my only -current machines are alphas, so I need to get gdb working again there first. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: How to dump a 4gig system on panic ?
Okay, seem to be about halfway there ... client kldload's no problem, server runs ... do a ctl-alt-esc to get into DDB and type panic, and it gives a message that its looking for the server and it finds it on the right IP ... then it prints out a '1023' and finishes the panic ... On the 'dump server', a vmcore gets created, but its zero length ... thoughts? On Fri, 17 May 2002, Andrew Gallatin wrote: Marc G. Fournier writes: Well, downloaded the files (a .tar.gz would be nice? *grin*) and the client built perfectly, and kldload worked fine ... is there some way someone can suggest of 'simulating a crash'? Some way to test to make sure that it is working as expected? I have a 4.6-PRE machine on my desk that I'd like to test with before I try it on the real thing, if at all possible? break into ddb do: ddb call dumpsys() Unless you're running a savecore which supports partial dumps, you need to disable partial dumps (sysctl net.net_dump.partial=0). And remember, you'll be spewing the contents of your ram (possibly passwords, etc) across the network in clear text. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
On Mon, 22 Apr 2002, Terry Lambert wrote: Marc G. Fournier wrote: First, alot of this stuff is slowly sinking in ... after repeatedly reading it and waiting for the headache to disapate:) But, one thing that I'm still not clear on ... If I have 4Gig of RAM in a server, does it make any sense to have swap space on that server also? Yes. But it (mostly) does not apply to KVA, only to UVA data, and there are much larger KVA requirements, so the more RAM you have, the bigger the bottleneck to user space for anything you swap. Okay ... to me, a bottleneck generally means slowdown ... so the more RAM I have, the slower the system will perform? Again, from what I'm reading, I have a total of 4Gig *aggregate* to work with, between RAM and swap, but its right here that I'm confused right now ... basically, the closer to 4Gig of RAM you get, the closer to 0 of swap you can have? No. I think you are getting confused on cardinality. You get one KVA, but you get an arbitrary number of UVA's, until you run out of physical RAM to make new ones. You have 4G aggregate KVA + UVA. So if your KVA is 3G, and your UVA is 1G, then you can have 1 3G KVA, and 1000 1G UVA's. Okay, first question here ... above you say 'arbitrary number of UVAs', but here you state 1000 ... just a number picked out of the air, or is this some fixed limit? Certain aspects of KVA are non-swappable. Some parts of UVA are swappable in theory, but never swapped in practice (the page tables and descriptors for each user process). The closer to 4G you have, the more physical RAM you have to spend on managing the physical RAM. The total amount of physical RAM you have to spend on managing memory is based on the total physical RAM plus the total swap. Okay, this makes sense ... I notice in 4.5-STABLE that if maxusers is set to 0, then the system will auto-tune based on memory ... is this something that also is auto-tuned? As soon as that number exceeds ~2.5G, you can't do it on a 32 bit processor any more, unless you hack FreeBSD to swap the VM housekeeping data it uses for swapping UVA contents. Okay, now here you lost me ... which number exceeds ~2.5G? The total amount of physical RAM you have to spend? Think of physical RAM as a resource. It's seperate from the KVA and UVA, but the KVA has to have physical references to do paged memory management. You are limited by how many of these you can have in physical RAM, total. Okay ... alot of lights came on simultaneously with this email ... some of those lights, mind you, might be false, but its a start ... If I'm understanding this at all ... the KVA (among other things) is a pre-allocated/reserved section of RAM for managing the UVAs ... simplistically, it maintains the process list and all resources associated with it ... I realize it does do alot of other things, but this is what I'm more focused on right now ... Now, what exactly is a UVA? You state above '1000 1G UVAs' ... is one process == 1 UVA? Or is one user (with all its associated processes) == 1 UVA? Next, again, if I'm reading this right ... if I set my KVA to 3G, when the system boots, it will reserve 3G of *physical* RAM for the kernel itself, correct? So on a 4G machine, 1G of *physical* RAM will be available for UVAs ... so, if I run 1G worth of processes, that is where swapping to disk comes in, right? Other then the massive performance hit, and the limit you mention about some parts of UVA not being swappable, I could theoretically have 4G of swap to page out to? Is there a reason why this stuff isn't auto-scaled based on RAM as it is? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
On Mon, 22 Apr 2002, Terry Lambert wrote: Marc G. Fournier wrote: On Sun, 21 Apr 2002, Terry Lambert wrote: No, there's no stats collected on this stuff, because it's a pretty obvious and straight-forward thing: you have to have a KVA space large enough that, once you subtract out 4K for each 4M of physical memory and swap (max 4G total for both), you end up with memory left over for the kernel to use, and your limits are such that the you don't run out of PTEs before you run out of mbufs (or whatever you plan on allocating). God, I'm glad its straightforwards :) Okay, first off, you say (max 4G total for both) ... do you max *total* between the two, or phy can be 4g *plus* swap can be 4g for a total of 8g? You aren't going to be able to exceed 4G, no matter what you do, because that's the limit of your address space. If you want more, then you need to use a 64 bit processor (or use a processor that supports bank selection, and hack up FreeBSD to do bank swapping on 2G at a time, just like Linux has been hacked up, and expect that it won't be very useful). Now I'm confused ... from what I've read so far, going out and buying an IBM eSeries 350 with 16Gig of RAM with Dual-PIII processors and hoping to run FreeBSD on it is not possible? Or, rather, hoping to use more then 4 out of 16Gig of RAM is? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
First, alot of this stuff is slowly sinking in ... after repeatedly reading it and waiting for the headache to disapate:) But, one thing that I'm still not clear on ... If I have 4Gig of RAM in a server, does it make any sense to have swap space on that server also? Again, from what I'm reading, I have a total of 4Gig *aggregate* to work with, between RAM and swap, but its right here that I'm confused right now ... basically, the closer to 4Gig of RAM you get, the closer to 0 of swap you can have? On Mon, 22 Apr 2002, Terry Lambert wrote: Marc G. Fournier wrote: No, there's no stats collected on this stuff, because it's a pretty obvious and straight-forward thing: you have to have a KVA space large enough that, once you subtract out 4K for each 4M of physical memory and swap (max 4G total for both), you end up with memory left over for the kernel to use, and your limits are such that the you don't run out of PTEs before you run out of mbufs (or whatever you plan on allocating). ... and translated to english, this means? :) Okay, I'm going to assume that I'm allowed 4Gig of RAM + 4Gig of Swap, for a total of 8Gig ... so, if I subtract out 4K for each 4M, that is 8M for ... what? So, I've theoretically got 8184M of VM available for the kernel to use right now? what are PTEs and how do I know how many I have right now? as for mbufs, I've currently got: No. Each 4M of physical memory takes 4K of statically allocated KVA. Each 4M of backing store takes 4K of statically allocated KVA. The definition of backing store includes: o All dirty data pages in swap o All dirty code pages in swap o All clean data pages in files mapped into process or kernel address space o All clean code pages for executables mapped into process or kernel address space o Reserved mappings for copy-on-write pages that haven't yet been written A PTE is a page table entry. It's the 32 bit value in the page table for each address space (one for the kernel, one per process). See the books I posted the titles of for more details, or read the Intel processor PDF's from their developer web site. jupiter netstat -m 173/1664/61440 mbufs in use (current/peak/max): 77 mbufs allocated to data 96 mbufs allocated to packet headers 71/932/15360 mbuf clusters in use (current/peak/max) 2280 Kbytes allocated to network (4% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines So how do I find out where my PTEs are sitting at? The mbufs are only important because most people allocate a large number of mbufs up front for networking applications, or for alrge numbers of users with network applications that will need resources in order to be able to actually run. There's also protocol control blocks and other allocation that occur up front, based on the maximum number of system open files and sockets you intend to permit. The user space stuff is generally a lot easier to calculate: do a ps -gaxl, round each entry in the VSZ column up to 4M, divide by 4K, and that tells you how many 4K units you have allocated for user space. For kernel space, the answer is that there are some allocated at boot time, (120M worth), and then the kernel map is grown, as necessary, until it hits the KVA space limit. If you plan on using up every byte, then divide your total KVA space by 4K to get the number of 4K pages allocated there. For the kernel stuff... you basically need to know where the kernel puts how much memory, based on the tuning parameters you use on it. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
On Sun, 21 Apr 2002, Terry Lambert wrote: No, there's no stats collected on this stuff, because it's a pretty obvious and straight-forward thing: you have to have a KVA space large enough that, once you subtract out 4K for each 4M of physical memory and swap (max 4G total for both), you end up with memory left over for the kernel to use, and your limits are such that the you don't run out of PTEs before you run out of mbufs (or whatever you plan on allocating). God, I'm glad its straightforwards :) Okay, first off, you say (max 4G total for both) ... do you max *total* between the two, or phy can be 4g *plus* swap can be 4g for a total of 8g? For instance, right now, I have 3Gig of physical and ~3gig of swap allocated ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
On Sun, 21 Apr 2002, Terry Lambert wrote: Marc G. Fournier wrote: You have more memory than you can allocate kernel memory to provide page table entries for. The only solution is to increase your kernel virtual address space size to accomodate the page mappings. How to do this varies widely by the version of FreeBSD you are using, and, unless you read NOTES and are running a recent -current, is not incredibly well documented, and requires an understanding of how the virtual address space is laid out and managed (which is also not well documented anywhere). Ya, this is the roadblock I'm hitting :( I'm running 4.5-STABLE here, as of this afternoon ... thoughts/suggestiosn based on that? Read the handbook as it existed for 4.5-STABLE, and read NOTES. It (sorta) tells you how to increase your KVA size. Also, is there somethign that I can run to monitor this, similar to running netstat -m to watch nmbclusters? DDB? 8-) 8-). No, there's no stats collected on this stuff, because it's a pretty obvious and straight-forward thing: you have to have a KVA space large enough that, once you subtract out 4K for each 4M of physical memory and swap (max 4G total for both), you end up with memory left over for the kernel to use, and your limits are such that the you don't run out of PTEs before you run out of mbufs (or whatever you plan on allocating). ... and translated to english, this means? :) Okay, I'm going to assume that I'm allowed 4Gig of RAM + 4Gig of Swap, for a total of 8Gig ... so, if I subtract out 4K for each 4M, that is 8M for ... what? So, I've theoretically got 8184M of VM available for the kernel to use right now? what are PTEs and how do I know how many I have right now? as for mbufs, I've currently got: jupiter netstat -m 173/1664/61440 mbufs in use (current/peak/max): 77 mbufs allocated to data 96 mbufs allocated to packet headers 71/932/15360 mbuf clusters in use (current/peak/max) 2280 Kbytes allocated to network (4% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines So how do I find out where my PTEs are sitting at? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
Over the past week, I've been trying to get information on how to fix a server that panics with: | panic: vm_map_entry_create: kernel resources exhausted | mp_lock = 0101; cpuid = 1; lapic.id = 0100 | boot() called on cpu#1 Great ... but, how do I determine what 'resources' I need to increase to avoid that crash? I've tried increasing maxusers from 512-1024, but *if* that works, I imagine I'm raising a bunch of limits (and using memory) that I don't have to ... The server is a Dual-CPU PIII-1Ghz with 3Gig of RAM and ~3Gig of swap space right now ... the data drive is 5x18gig drives in a RAID5 configuration (hardware RAID, not vinum) ... I ran top in an xterm so that I could see what was up just before the crash, and the results were: last pid: 84988; load averages: 19.82, 57.35, 44.426 up 0+23:33:12 02:05:00 5021 processes:16 running, 5005 sleeping CPU states: 8.7% user, 0.0% nice, 24.3% system, 2.2% interrupt, 64.7% idle Mem: 2320M Active, 211M Inact, 390M Wired, 92M Cache, 199M Buf, 4348K Free Swap: 3072M Total, 1048M Used, 2024M Free, 34% Inuse, 448K Out So, I have plenty of swapspace left, lots of idle CPU and a whole whack of processes ... Now, looking at the LINT file, there appears to be *alot* of things I *could* change ... for instance, NSFBUFS, KVA_FILES, etc ... but I don't imagine that changing these blindly is particularly wise ... so, how do you determine what to change? For instance, at a maxusers of 512, NSFBUFS should be ~8704, and if I've only got 5000 processes running, chances are I'm still safe at that value, no? But sysctl doesn't show any 'sf_buf' value, so how do I figure out what I'm using? Basically, are there any commands similar to netstat -m for nmbclusters that I can run to 'monitor' and isolate where I'm exhausting these resources? Is there a doc on this sort of stuff that I should be reading for this? Something that talks about kernel tuning for high-load/processes servers? Thanks for any help in advance .. --- machine i386 cpu I686_CPU ident kernel maxusers1024 options NMBCLUSTERS=15360 options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM options SHMMAXPGS=98304 options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) options SYSVSEM options SEMMNI=2048 options SEMMNS=4096 options SYSVMSG #SYSV-style message queues options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM#Rate limit bad replies options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa device pci device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device amr # AMI MegaRAID device sym device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0at atkbdc? irq 12 device vga0at isa? pseudo-device splash device sc0 at isa? flags 0x100 device npx0at nexus? port IO_NPX irq 13 device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) pseudo-device loop# Network loopback pseudo-device ether # Ethernet support pseudo-device pty 256 # Pseudo-ttys (telnet etc) pseudo-device gif # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) pseudo-device bpf #Berkeley packet filter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
As a quick follow-up to this, doing more searching on the web, I came across a few suggested 'sysctl' settings, which I've added to what I had before, for a total of: kern.maxfiles=65534 jail.sysvipc_allowed=1 vm.swap_idle_enabled=1 vfs.vmiodirenable=1 kern.ipc.somaxconn=4096 I've also just reduced my maxusers to 256 from 1024, since 1024 was crashing worse then 512, and I ran across the 'tuning' man page that stated that you shouldn't go above 256 :( Just a bit more detail on the setup ... On Sat, 20 Apr 2002, Marc G. Fournier wrote: Over the past week, I've been trying to get information on how to fix a server that panics with: | panic: vm_map_entry_create: kernel resources exhausted | mp_lock = 0101; cpuid = 1; lapic.id = 0100 | boot() called on cpu#1 Great ... but, how do I determine what 'resources' I need to increase to avoid that crash? I've tried increasing maxusers from 512-1024, but *if* that works, I imagine I'm raising a bunch of limits (and using memory) that I don't have to ... The server is a Dual-CPU PIII-1Ghz with 3Gig of RAM and ~3Gig of swap space right now ... the data drive is 5x18gig drives in a RAID5 configuration (hardware RAID, not vinum) ... I ran top in an xterm so that I could see what was up just before the crash, and the results were: last pid: 84988; load averages: 19.82, 57.35, 44.426 up 0+23:33:12 02:05:00 5021 processes:16 running, 5005 sleeping CPU states: 8.7% user, 0.0% nice, 24.3% system, 2.2% interrupt, 64.7% idle Mem: 2320M Active, 211M Inact, 390M Wired, 92M Cache, 199M Buf, 4348K Free Swap: 3072M Total, 1048M Used, 2024M Free, 34% Inuse, 448K Out So, I have plenty of swapspace left, lots of idle CPU and a whole whack of processes ... Now, looking at the LINT file, there appears to be *alot* of things I *could* change ... for instance, NSFBUFS, KVA_FILES, etc ... but I don't imagine that changing these blindly is particularly wise ... so, how do you determine what to change? For instance, at a maxusers of 512, NSFBUFS should be ~8704, and if I've only got 5000 processes running, chances are I'm still safe at that value, no? But sysctl doesn't show any 'sf_buf' value, so how do I figure out what I'm using? Basically, are there any commands similar to netstat -m for nmbclusters that I can run to 'monitor' and isolate where I'm exhausting these resources? Is there a doc on this sort of stuff that I should be reading for this? Something that talks about kernel tuning for high-load/processes servers? Thanks for any help in advance .. --- machine i386 cpu I686_CPU ident kernel maxusers 1024 options NMBCLUSTERS=15360 options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM options SHMMAXPGS=98304 options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) options SYSVSEM options SEMMNI=2048 options SEMMNS=4096 options SYSVMSG #SYSV-style message queues options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM#Rate limit bad replies options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O deviceisa devicepci devicescbus # SCSI bus (required) deviceda # Direct Access (disks) devicesa # Sequential Access (tape etc) devicecd # CD devicepass# Passthrough device (direct SCSI access) deviceamr # AMI MegaRAID device sym deviceatkbdc0 at isa? port IO_KBD deviceatkbd0 at atkbdc? irq 1 flags 0x1 devicepsm0at atkbdc? irq 12 devicevga0at isa? pseudo-device splash devicesc0 at isa? flags 0x100 devicenpx0at nexus? port IO_NPX irq 13 devicesio0at isa? port IO_COM1 flags 0x10 irq 4 devicesio1at isa? port IO_COM2 irq 3 devicemiibus # MII bus support devicefxp # Intel
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
On Sat, 20 Apr 2002, Alfred Perlstein wrote: * The Hermit Hacker [EMAIL PROTECTED] [020420 16:01] wrote: As a quick follow-up to this, doing more searching on the web, I came across a few suggested 'sysctl' settings, which I've added to what I had before, for a total of: kern.maxfiles=65534 jail.sysvipc_allowed=1 vm.swap_idle_enabled=1 vfs.vmiodirenable=1 kern.ipc.somaxconn=4096 I've also just reduced my maxusers to 256 from 1024, since 1024 was crashing worse then 512, and I ran across the 'tuning' man page that stated that you shouldn't go above 256 :( Just a bit more detail on the setup ... You said you're running 5000 processes. 5000 processes of what? Are they useing SYSVSHM? If so, this sysctl might help: kern.ipc.shm_use_phys=1 Okay, never knew of that one before ... have it set for the next reboot, as I do have a few postgresql servers going on the 'root (non-jail)' server ... It'll only work if you set it before your processes setup. Some more information about what these 5000 processes are doing would help. Sorry ... the server is running ~210 jails ... so the '5k processes' would be when they all start up their periodic scripts ... normally, it hovers around 2700 processes ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
On Sat, 20 Apr 2002, Terry Lambert wrote: Marc G. Fournier wrote: Over the past week, I've been trying to get information on how to fix a server that panics with: | panic: vm_map_entry_create: kernel resources exhausted | mp_lock = 0101; cpuid = 1; lapic.id = 0100 | boot() called on cpu#1 Great ... but, how do I determine what 'resources' I need to increase to avoid that crash? I've tried increasing maxusers from 512-1024, but *if* that works, I imagine I'm raising a bunch of limits (and using memory) that I don't have to ... The server is a Dual-CPU PIII-1Ghz with 3Gig of RAM and ~3Gig of swap space right now ... the data drive is 5x18gig drives in a RAID5 configuration (hardware RAID, not vinum) ... You have more memory than you can allocate kernel memory to provide page table entries for. The only solution is to increase your kernel virtual address space size to accomodate the page mappings. How to do this varies widely by the version of FreeBSD you are using, and, unless you read NOTES and are running a recent -current, is not incredibly well documented, and requires an understanding of how the virtual address space is laid out and managed (which is also not well documented anywhere). Ya, this is the roadblock I'm hitting :( I'm running 4.5-STABLE here, as of this afternoon ... thoughts/suggestiosn based on that? Also, is there somethign that I can run to monitor this, similar to running netstat -m to watch nmbclusters? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic: fdrop: count 0
based on source code cvsup'd today:
panic+0xc8
fdrop+0x32
closef+0x9b
close+0x89
syscall+0x645
syscall_with_err_pushd+0x1b
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: panic: fdrop: count 0
Just tried to do a buildworld with a May 24th kernel and it did it there
also ...
On Sun, 27 May 2001, Marc G. Fournier wrote:
based on source code cvsup'd today:
panic+0xc8
fdrop+0x32
closef+0x9b
close+0x89
syscall+0x645
syscall_with_err_pushd+0x1b
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
latest panic ... procrunnable?
thank god for digital cameras ... current panic was while doing a simple
'make buildworld', no -j option ... based on most recent sources ...
cpid = 0; lapic.id =
instruction pointer = 0x8:0xc0179309
stack pointer = 0x10:0xcb350f60
frame pointer = 0x10:0xcb350f64
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, IOPL - 0
current process = 11 (idle: cpu0)
kernel: type 29 trap, code=0
Stopped at procrunnable+0xd: movl%ebp,%esp
db trace
procrunnable+0xd
idle_proc+0x1e
fork_exit+0xbc
fork_trampoline+0x8
db show pcpu 0
cpuid = 0
curproc = 0xcb346840: pid 11 idle: cpu0
curpcb = 0xcb34f000
npxproc = none
idleproc = 0xcb346840: pid 11 idle: cpu0
db show pcpu 1
cpuid = 1
curproc = 0xccf860e0: pid 37362 cpp0
curpcb = 0xccfe6000
npxproc = none
idleproc = 0xcb346a60: pid 10 idle: cpu1
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Bad superblock on file systems ...
anyone having a problem with that with -current kernels? where the kernel
panics, on reboot the superblock is screwed ... I can do a 'mount -a' to
recalculate, then an umount -a and 'fsck -y' to clean the file systems ...
I have softupdates enabled on all file systems except for /, if that
helps?
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
buildworld fails in current ...
*just* cvsup'd latest code ...
cd /usr/src/gnu/usr.bin/perl/libperl; make obj; make depend; make all; make install
/usr/obj/i386/usr/src//usr/src/gnu/usr.bin/perl/libperl created for
/usr/src/gnu/usr.bin/perl/libperl
Can't find config.sh.
*** Error code 1
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
can't get into single user mode - panic: ffs_valloc: dup alloc
morning all ...
Well, I swear I have to be missing something here that is going to
make me slap my forehead, but I can't get into single user mode :(
I hit the space bar, type in 'boot -s' and it goes through all the
normal start up procedures, sets up the networking, etc ...
The reason I'm trying to get into single user mode is cause I
can't get into multi-user without it doing:
=
Recovering vi editor sessions
mode = 0100600, inum = 729, fs = /tmp
panic: ffs_valloc: dup alloc
cpuid = 0; lapic.id =
Debugger("panic")
CPU0 stopping CPUs: 0x0002... stopped
and a trace of:
Debugger() @ +0x38
panic() @ +0xa0
ffs_valloc()@ +0xf5
ufs_makeinode() @ +0x5a
ufs_create()@ +0x28
ufs_vnoperate() @ +0x15
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: can't get into single user mode - panic: ffs_valloc: dup alloc
On Mon, 9 Oct 2000, Robert Watson wrote: On Mon, 9 Oct 2000, Marc G. Fournier wrote: Well, I swear I have to be missing something here that is going to make me slap my forehead, but I can't get into single user mode :( I hit the space bar, type in 'boot -s' and it goes through all the normal start up procedures, sets up the networking, etc ... The reason I'm trying to get into single user mode is cause I can't get into multi-user without it doing: That's interesting -- this morning, I hit a ffs_valloc: dup alloc panic following a buildworld. I assumed it was to do with my local ACL patches, although I have been unable to find a bug that could trigger it. I'm wondering if this isn't some sort of locking issue in VFS. I managed to trigger it in ufs_mkdir(), as I introduced a potentially location for blocking where previously none existed, suggesting that perhaps some UFS code is playing fast and loose with vnode locks. This panic is generated when FFS tries to recycle a vnode, but discovers it has a non-zero mode, indicating that it is in use elsewhere in the system, which should never happen. BTW, do you have FFS_EXTATTR enabled? not that I've enabled ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
latest ahc panic, more data ...
okay, have been watching the conversation going on in the committers list,
and am watching for any new commits that seem appropriate, but figure
adding a little bit of extra info as I come up with it might help?
latest reboot had a bit more info then the last, and started with:
ahc0:A:1: ahc_intr - referenced scb not valid during seqint 0x73 scb(147)
ach0: WARNING no command for scb 147 (cmdcmplt)
QOUTPOS=132
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: latest ahc panic, more data ...
there is a thread going on in committers that appears to revolve aroudn
this issue, and Justin has been throwing out patches, so it is being
worked on "fast and furious" ... I'm currently up in Windows (Dual-Boot
machine fo rmy little girl) watching for a physical commit to the
repository that at least suggestions its a fix before rebooting and
upgrading :)
On Sat, 7 Oct 2000, Bosko Milekic wrote:
I've just been hit by one such problem on bootup. This is -current as of
today, so I suspect it's the commits that went in the past two days.
Basically, I tracked it down just enough to know that the problem is
happening during a call to ahc_print_path() in aic7xxx.c, specifically
for me, this happens during bootup in ahc_handle_scsiint() right after
the second call to ahc_abort_scbs().
ahc_print_path() is called like this:
ahc_print_path(ahc, scb);
(why both ahc and scb are being passed, I have no idea, since
ahc_print_path only actually makes use of scb).
For the unaware, ahc_print_path() seems to only wrap a call to
xpt_print_path() to which it passes scb-io_ctx-ccb_h.path as an
argument, and in this case, scb-io_ctx happens to be NULL, so during its
pass, a NULL pointer gets dereferenced and the page fault happens.
The NULLing out of this is coming somewhere in ahc_handle_scsiint(),
because some prior ahc_print_path()s (with the same arguments) are
succeeding.
I have not tried backing out the changes from the past two days and
trying again, but this was not happening a week ago.
So what's going on here?
On Sat, 7 Oct 2000, Marc G. Fournier wrote:
okay, have been watching the conversation going on in the committers list,
and am watching for any new commits that seem appropriate, but figure
adding a little bit of extra info as I come up with it might help?
latest reboot had a bit more info then the last, and started with:
ahc0:A:1: ahc_intr - referenced scb not valid during seqint 0x73 scb(147)
ach0: WARNING no command for scb 147 (cmdcmplt)
QOUTPOS=132
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
Bosko Milekic
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
