Re: if_bge driver problem. - SOLVED
On Wed, Feb 01, 2006 at 10:27:43AM +0300, Gleb Smirnoff wrote: On Wed, Feb 01, 2006 at 09:11:22AM +0200, husnu demir wrote: h No I am not tired. We would like to be part of that, even like testers. I did try to compile but gave these error messages. I did not make CVSUP because of the pci error in the tree. You can CVSUP once more, the PCI issue is fixed already. h Here is the error messages; h h cc -O2 -fno-strict-aliasing -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/METU/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/usr/obj/usr/src/sys/METU -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/bge/../../dev/bge/if_bge.c h /usr/src/sys/modules/bge/../../dev/bge/if_bge.c: In function `bge_poll_locked': h /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:2749: error: structure has no member named `bge_link_evt' h /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:2754: error: structure has no member named `bge_link_evt' h /usr/src/sys/modules/bge/../../dev/bge/if_bge.c: In function `bge_intr': h /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:2806: error: structure has no member named `bge_link_evt' h /usr/src/sys/modules/bge/../../dev/bge/if_bge.c: In function `bge_tick_locked': h /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:2857: error: structure has no member named `bge_link_evt' h /usr/src/sys/modules/bge/../../dev/bge/if_bge.c: In function `bge_link_upd': h /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:3741: error: structure has no member named `bge_link_evt' Looks like the patch to if_bgereg.h wasn't applied. Can you reapply patches after cvsup? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] OK. Everything works for now with polling and without polling enabled. It can see the carrier status and UP/DOWN the interface. Thanks for the help. Husnu Demir. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient wedged
On Tue, 2006-Jan-31 15:38:53 -0500, Lodewijk Vge wrote: On 31-jan-2006, at 14:13, Brooks Davis wrote: At the very least I need a coredump and your executable so I can look at variables in receive_packet. I accidentally killed it with my attempts to make it dump a core file. so, what should I do the next time it happens to make it dump core? kill -QUIT ... is the generic answer. sigaction(2) provides the definitive list of which signals default to dumping core. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Change in Promise controllers
On Wed, 01 Feb 2006 16:33:24 +1300 Mark Kirkwood wrote: Not of much help to you I'm afraid :-( , but a couple of us see a very similar error with the SX4060 (PDC20621) - same chip as the SX4000 which works perfectly for Søren, so I'll be very interested to find out what is going on with this! Doesn't really help, correct. :-) In my case however, the chip isn't even the same. I'm not sure what exactly is happening here, but there seems to be one version of my controller out there with a PDC20775 (which I have[1]) and one with ad PDC40775. I don't know what the differences are, but since FreeBSD 6-STABLE was running (as such) until a few days ago (that's when the controller was recognized as a 40775), I am guessing that there is some difference in these chips, even if not much. Maybe I'll mess around with the code a little. :-) Regards Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI device timeout
Derkjan de Haan wrote: All, Today, after a cvsup (RELENG_6) and a rebuild of kernel and world, my system no longer boots. It hangs on Waiting 5 seconds for SCSI devices to settle Booting from the previous kernel allows my system to boot again. Please let me know if I can do anything to diagnose further. regards, Derkjan de Haan I have exactly the same problem here on a ASUS A7V333 Motherboard and an Adaptec 3960D SCSI Controller. The problem seems to be in the acpi interrupt routing, I've updated the mainboard Bios to the last available version in the meantime (1018.004 Beta) with no luck. Disabling acpi completly helps booting the machine again.. Regards, Holm -- LP::Kommunikation GbR Holm Tiffe * Administration, Development FreibergNet.de Internet Systems phone +49 3731 419010 Bereich Server Technik fax +49 3731 4196026 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI device timeout
Johan Ström wrote: On 1 feb 2006, at 10.57, Holm Tiffe wrote: Derkjan de Haan wrote: All, Today, after a cvsup (RELENG_6) and a rebuild of kernel and world, my system no longer boots. It hangs on Waiting 5 seconds for SCSI devices to settle Booting from the previous kernel allows my system to boot again. Please let me know if I can do anything to diagnose further. regards, Derkjan de Haan I have exactly the same problem here on a ASUS A7V333 Motherboard and an Adaptec 3960D SCSI Controller. The problem seems to be in the acpi interrupt routing, I've updated the mainboard Bios to the last available version in the meantime (1018.004 Beta) with no luck. Disabling acpi completly helps booting the machine again.. Hi I got one of those motherboards.. however no SCSI card but a promise. Ive hade huge problems with it (check out the Page fault, GEOM problem?? thread). The problems i had was random crashes and very bad speed to the disks. It was solved by throwing the mobo out with a new one with nforce2 chipset... Got great speeds now and haven't had a crash since i installed it (roughly a week now). Johan Ström [EMAIL PROTECTED] http://www.stromnet.org/ No Johan, my A7V333 has no problem, it runs for arounrd 2 years now as my personal workstation here at work 24/7. I've cvsupped RELENG_6 again for an hour or so and the now build kernel runs flawlessly. There are some new patches in the pci code. Regards, Holm -- LP::Kommunikation GbR Holm Tiffe * Administration, Development FreibergNet.de Internet Systems phone +49 3731 419010 Bereich Server Technik fax +49 3731 4196026 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI device timeout
On 1 feb 2006, at 11.42, Holm Tiffe wrote: Johan Ström wrote: On 1 feb 2006, at 10.57, Holm Tiffe wrote: Derkjan de Haan wrote: All, Today, after a cvsup (RELENG_6) and a rebuild of kernel and world, my system no longer boots. It hangs on Waiting 5 seconds for SCSI devices to settle Booting from the previous kernel allows my system to boot again. Please let me know if I can do anything to diagnose further. regards, Derkjan de Haan I have exactly the same problem here on a ASUS A7V333 Motherboard and an Adaptec 3960D SCSI Controller. The problem seems to be in the acpi interrupt routing, I've updated the mainboard Bios to the last available version in the meantime (1018.004 Beta) with no luck. Disabling acpi completly helps booting the machine again.. Hi I got one of those motherboards.. however no SCSI card but a promise. Ive hade huge problems with it (check out the Page fault, GEOM problem?? thread). The problems i had was random crashes and very bad speed to the disks. It was solved by throwing the mobo out with a new one with nforce2 chipset... Got great speeds now and haven't had a crash since i installed it (roughly a week now). Johan Ström [EMAIL PROTECTED] http://www.stromnet.org/ No Johan, my A7V333 has no problem, it runs for arounrd 2 years now as my personal workstation here at work 24/7. I've cvsupped RELENG_6 again for an hour or so and the now build kernel runs flawlessly. There are some new patches in the pci code. Regards, Holm -- LP::Kommunikation GbR Holm Tiffe * Administration, Development FreibergNet.de Internet Systems phone +49 3731 419010 Bereich Server Technik fax +49 3731 4196026 D-09599 Freiberg * Am St. Niclas Schacht 13 http:// www.freibergnet.de Hi, yes I've been running it for around 2-3 years too, but with linux. A couple of months ago I switched to fbsd and problems began to occur. Might not be the same problem however.. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Quota deadlocks.
I'm not able to reproduce the quota deadlocks that were reported. Can anyone reproduce them on 7.0? I need more specific instructions on how to reproduce, or more detailed debugging info from someone who can. If you can reproduce, please add 'options DEBUG_LOCKS' to your kernel. Then get me the output of 'alltrace' 'ps' and 'show lockedvnods' from ddb. I'll also need the output of 'mount' and a good description of what triggered the issue. I hope to resolve this before 6.1. Cheers, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Restartable system call behaviour
I have a piece of coode which does some networking, in which I see read and write calls failing with 'Interrupted system call' from time to time. The reason it puzzles me is that I am explicitly catching every signal that could possibly be causing this, with the SA_RESTART flag set. So surely I should never see this ? This only started happening when we moved away from 4.11 - it was happening the whole time I was running on 5.4 and still happens on 6.0. I thought that the default was for restartable system calls - I only started setting the SA_RESTART flag explicitly in the last 24 hours in an effort to fix this, but it is still happening. Have I missed something fundamental about signals and system calls ? I am about to go in and adapt my code so that it retries the system call if it is interrupted - but I am uneasy about doing this without knowing *why* the system calls arent't restarting automaticly. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6-stable and HTT P4
Just got it to work though... Had to add machdep.hyperthreading_allowed=1 to loader.conf in addition to hlt_logical_cpus=0 Great. FYI, HTT will give you little or even negative performance benefits. Heh - I still cant persuade my 6.0-RELEASE to *not* use hyperthreading! have got hyperthreading_allowed set to 0, hlt_logical_cpus set to 1 and it sttill shcedules things on 4 CPU's rather than 2. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: top doesn't show any Process in idle-Mode
Hello, sorry for the time ago, i haven't an FreeBSD-Box on my Work. The CLI-Optin -S doesn't really help me. I will test the patch from Stefan Esser, but i think my Problem are not alone SRUN-Proc's. if i run TOP with the CLI-Options -I -S so i should see Processes with status RUN and SRUN, if i was right. I have also running top described as above, and now i do a make -j 16 cleen cleandir cleandepend under /usr/src, so i unterstand things right i shoud see minimum 3 or more Processes with status RUN ( System was Sempron 2400 @1800MHz). But i shows only one and this very short, but if the system runs i could see an process named pagex, and if the system was idle i can see an process with status SRUN called idle So i get the time i will test the Patch from Stefan. If i getting new values and experiences i come back again. Tahnks to all and best regards michael 2006/1/30, Stefan Esser [EMAIL PROTECTED]: On 2006-01-30 13:49 +0100, Michael Schuh [EMAIL PROTECTED] wrote: Hello, i use top mostly in idle-mode. # top return i or # top -I Under releng_6 (stable p4) and the older versions, i think down to releng_5, doesn't show a running process. I have tryed to dig in the source but my experiences are not so good that i can find the possible error. See line 603 (in HEAD) of /usr/src/usr.bin/top/machine.c: if (displaymode == DISP_CPU !show_idle (pp-ki_pctcpu == 0 || pp-ki_stat != SRUN)) /* skip idle or non-running processes */ continue; Since I do not like the current behaviour, I considered removing the test for state SRUN. But I guess that the teest can not be completely eliminated. Instead of selecting only SRUN, some states may need to be suppressed (SZOMB, possibly also SIDL, SSTOP). I'll test the following version on my system: if (displaymode == DISP_CPU !show_idle (pp-ki_pctcpu == 0 || pp-ki_stat == SZOMB || pp-ki_stat == SSTOP)) /* skip idle or non-running processes */ continue; Has anyone same experiences made with top, or has anyone a workaround (please not like while true) Patch included (not verified to apply to 5.x or 6.x, but editing the test in place should be easy, then). Regards, STefan --- /usr/src/usr.bin/top/machine.c 18 May 2005 13:42:51 - 1.74 +++ /usr/src/usr.bin/top/machine.c 30 Jan 2006 14:26:08 - @@ -601,7 +601,7 @@ continue; if (displaymode == DISP_CPU !show_idle - (pp-ki_pctcpu == 0 || pp-ki_stat != SRUN)) + (pp-ki_pctcpu == 0 || pp-ki_stat == SZOMB || pp-ki_stat == SSTOP)) /* skip idle or non-running processes */ continue; ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Update: Change in Promise controllers (is the source-code broken?)
I mounted ad8 as ro and tried to copy files off that drive. Didn't do much good, the system still hung up. Because of the -ro I thought it might be possible to shutdown the system cleanly, but that didn't work this time either. During shutdown the fushing of the cache fails. Strangely, this time the system also complained about a Robinson for ad2. What really freaks me out about this is for one ad2 is connected to the southbridge (as the device-name suggests) and that nothing on ad2 was ever mounted in this session. What changed in the code? Regards Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Quota deadlocks.
Hi. On Wed, Feb 01, 2006 at 03:36:19AM -0800, Jeff Roberson wrote: I'm not able to reproduce the quota deadlocks that were reported. Can anyone reproduce them on 7.0? I need more specific instructions on how to reproduce, or more detailed debugging info from someone who can. If you can reproduce, please add 'options DEBUG_LOCKS' to your kernel. Then get me the output of 'alltrace' 'ps' and 'show lockedvnods' from ddb. I'll also need the output of 'mount' and a good description of what triggered the issue. I hope to resolve this before 6.1. I have no chance to test on 7 and currently try to avoid crashing our NFS server. I have good reasons to believe, that the problem also occurs on UP machines (see my postings in Reply to Henri Hennebert (Re: 6.0-RELEASE freeze repetitively). Unfortunately, the server has no DEBUG_LOCKS turned on :-/ I cannot see any load problem or any cronjob making traffic. Close to the time of the crash I see an ftp user on one of our app servers, that might have reached his quota (rquotad, NFS), though I cannot tell for sure. And also it's unlikely that this is the only time someone reached his quota. If there's apart from what I posted something I could look up in the dump, then please tell me. Thanx for looking into this, Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | pgpVXu7NzSYFp.pgp Description: PGP signature
Re: SCSI device timeout
Derkjan de Haan wrote: Today, after a cvsup (RELENG_6) and a rebuild of kernel and world, my system no longer boots. It hangs on Waiting 5 seconds for SCSI devices to settle Booting from the previous kernel allows my system to boot again. Please let me know if I can do anything to diagnose further. I have exactly the same problem here on a ASUS A7V333 Motherboard and an Adaptec 3960D SCSI Controller. The problem seems to be in the acpi interrupt routing, I've updated the mainboard Bios to the last available version in the meantime (1018.004 Beta) with no luck. Disabling acpi completly helps booting the machine again.. On my system, the problem was gone with version 1.292.2.7 of src/sys/dev/pci pci.c, committed on 2006-01-31 14:42:43 UTC. So perhaps it's a good idea to cvsup and rebuild again, to see if everything works again. regards, Derkjan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
KDE 3.5
Hey, where can i get it from with pkg_add ?? thx, roger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hi all.. Novice user having woes getting Atheros card up in FreeBSD 6.0
There is a problem with country code in DWL-AG530, you can solve setting country code, we can find instructions for this in: http://madwifi.org/wiki/Compatibility Our newest DWL-AG530 are working now on FreeBSD 5.4 and FreeBSD 6.0: FreeBSD 5.4 before load contry code: Jan 4 19:39:04 dl2 kernel: ath0: Atheros 5212 mem 0xee00-0xee00 irq 10 at device 8.0 on pci0 Jan 4 19:39:04 dl2 kernel: ath0: mac 5.9 phy 4.3 5ghz radio 3.6 Jan 4 19:39:04 dl2 kernel: ath0: unable to collect channel list from hal Jan 4 19:39:04 dl2 kernel: device_attach: ath0 attach returned 22 After set country code: Jan 11 15:10:19 dl2 kernel: ath0: Atheros 5212 mem 0xee00-0xee00 irq 10 at device 8.0 on pci0 Jan 11 15:10:19 dl2 kernel: ath0: mac 5.9 phy 4.3 5ghz radio 3.6 Jan 11 15:10:19 dl2 kernel: ath0: Ethernet address: 00:13:46:9a:29:18 Jan 11 15:10:19 dl2 kernel: ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 11 15:10:19 dl2 kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Jan 11 15:10:19 dl2 kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 11 15:10:19 dl2 kernel: ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Paulo Fragoso. Derek Evans wrote: I think the newest D-link DWL-AG530 must use the AR5213 chipset too. Before I got it I had done some checking and read somewhere that it used the AR5212, so I thought I'd be ok. When I tried it recently I got: FreeBSD rock 6.0-STABLE FreeBSD 6.0-STABLE #1: Sun Jan 22 10:45:11 EST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/ROCK i386 ... ath0: Atheros 5212 mem 0xea00-0xea00 irq 11 at device 17.0 on pci0 ath0: unable to collect channel list from hal; regdomain likely 18 country code 0 device_attach: ath0 attach returned 22 I haven't tried Sam's patches yet. I'm assuming they're still current though. I have instructions for getting the patches, applying the patches, and testing them. I'll send them to you via BSDForums (since that's where they're saved). Can you point me to these instructions as well please? Yes, I already looked. :) -derek ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5
Follow the instructions at http://freebsd.kde.org/ On 2/1/06, Roger Grosswiler [EMAIL PROTECTED] wrote: Hey, where can i get it from with pkg_add ?? thx, roger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- // Irvin P. Piraman // http://netgarage.thefluxproject.com // Key ID: 0x92CA572B ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5
Roger Grosswiler schrieb: Hey, where can i get it from with pkg_add ?? http://www.freebsd.org/doc/en/books/handbook/packages-using.html Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: KDE 3.5
On Wed, Feb 01, 2006 at 02:52:56PM +0100, Michael Nottebrock wrote: Roger Grosswiler schrieb: Hey, where can i get it from with pkg_add ?? http://www.freebsd.org/doc/en/books/handbook/packages-using.html Unfortunately we're still playing catch-up with the official packages, though by now we had just about got kde 3.5.0 built and uploaded everywhere. The extensive testing we had to do for recent bsd.port.mk commits monopolized the build cluster for the past few weeks to the exclusion of other package builds, and then there were qt and other port build problems that have hopefully now been resolved. Unfortunately, now we are back to square 1, since you just committed KDE 3.5.1 :-) Kris pgp2q4V7mwbKN.pgp Description: PGP signature
Re: KDE 3.5
Kris Kennaway schrieb: Unfortunately, now we are back to square 1, since you just committed KDE 3.5.1 :-) 'S okay - patience is a virtue and package users are the most virtuous bunch of them all. And as for square one, expat2 got bumped. :O Cheers, -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org signature.asc Description: OpenPGP digital signature
Re: SCSI device timeout
On Feb 1, 2006, at 4:57 AM, Holm Tiffe wrote: The problem seems to be in the acpi interrupt routing, I've updated the mainboard Bios to the last available version in the meantime (1018.004 Beta) with no luck. Disabling acpi completly helps booting the machine again.. I'm suspecting I have the same issue with 6.0-REL (both CD and -p4 build locally) on a Dell PE800 server. Safe-mode boots ok, but otherwise it locks up. Curiously, the serial console is still responsive but the keyboard is not. I have a PR open for this: http://www.freebsd.org/cgi/query-pr.cgi? pr=91910 I'm trying disabling acpi now... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on sparc64/sparc64
TB --- 2006-02-01 15:43:51 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-02-01 15:43:51 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2006-02-01 15:43:51 - cleaning the object tree TB --- 2006-02-01 15:44:16 - checking out the source tree TB --- 2006-02-01 15:44:16 - cd /tinderbox/RELENG_6/sparc64/sparc64 TB --- 2006-02-01 15:44:16 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2006-02-01 15:54:31 - building world (CFLAGS=-O -pipe) TB --- 2006-02-01 15:54:31 - cd /src TB --- 2006-02-01 15:54:31 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2006-02-01 16:42:46 - generating LINT kernel config TB --- 2006-02-01 16:42:46 - cd /src/sys/sparc64/conf TB --- 2006-02-01 16:42:46 - /usr/bin/make -B LINT TB --- 2006-02-01 16:42:46 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2006-02-01 16:42:46 - cd /src TB --- 2006-02-01 16:42:46 - /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Feb 1 16:42:46 UTC 2006 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] === isp (all) cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/sparc64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=15000 -fno-common -I/obj/sparc64/src/sys/LINT -mcmodel=medlow -msoft-float -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/isp/../../dev/isp/isp.c cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/sparc64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=15000 -fno-common -I/obj/sparc64/src/sys/LINT -mcmodel=medlow -msoft-float -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/isp/../../dev/isp/isp_target.c /src/sys/modules/isp/../../dev/isp/isp_target.c: In function `isp_target_notify': @/dev/isp/isp_inline.h:1272: warning: inlining failed in call to 'isp_get_ctio': --param large-function-growth limit reached /src/sys/modules/isp/../../dev/isp/isp_target.c:163: warning: called from here @/dev/isp/isp_inline.h:1203: warning: inlining failed in call to 'isp_get_atio2e': --param large-function-growth limit reached /src/sys/modules/isp/../../dev/isp/isp_target.c:168: warning: called from here *** Error code 1 Stop in /src/sys/modules/isp. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-02-01 16:53:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-02-01 16:53:26 - ERROR: failed to build lint kernel TB --- 2006-02-01 16:53:26 - tinderbox aborted TB --- 0.81 user 3.84 system 4174.68 real ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [releng_6 tinderbox] failure on sparc64/sparc64
This is failing since January 26. Shouldn't RELENG_6 build, especially while we're preparing a release? harti On Wed, 1 Feb 2006, FreeBSD Tinderbox wrote: FTTB --- 2006-02-01 15:43:51 - tinderbox 2.3 running on freebsd-current.sentex.ca FTTB --- 2006-02-01 15:43:51 - starting RELENG_6 tinderbox run for sparc64/sparc64 FTTB --- 2006-02-01 15:43:51 - cleaning the object tree FTTB --- 2006-02-01 15:44:16 - checking out the source tree FTTB --- 2006-02-01 15:44:16 - cd /tinderbox/RELENG_6/sparc64/sparc64 FTTB --- 2006-02-01 15:44:16 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src FTTB --- 2006-02-01 15:54:31 - building world (CFLAGS=-O -pipe) FTTB --- 2006-02-01 15:54:31 - cd /src FTTB --- 2006-02-01 15:54:31 - /usr/bin/make -B buildworld FT Rebuilding the temporary build tree FT stage 1.1: legacy release compatibility shims FT stage 1.2: bootstrap tools FT stage 2.1: cleaning up the object tree FT stage 2.2: rebuilding the object tree FT stage 2.3: build tools FT stage 3: cross tools FT stage 4.1: building includes FT stage 4.2: building libraries FT stage 4.3: make dependencies FT stage 4.4: building everything FTTB --- 2006-02-01 16:42:46 - generating LINT kernel config FTTB --- 2006-02-01 16:42:46 - cd /src/sys/sparc64/conf FTTB --- 2006-02-01 16:42:46 - /usr/bin/make -B LINT FTTB --- 2006-02-01 16:42:46 - building LINT kernel (COPTFLAGS=-O -pipe) FTTB --- 2006-02-01 16:42:46 - cd /src FTTB --- 2006-02-01 16:42:46 - /usr/bin/make buildkernel KERNCONF=LINT FT Kernel build for LINT started on Wed Feb 1 16:42:46 UTC 2006 FT stage 1: configuring the kernel FT stage 2.1: cleaning up the object tree FT stage 2.2: rebuilding the object tree FT stage 2.3: build tools FT stage 3.1: making dependencies FT stage 3.2: building everything FT[...] FT=== isp (all) FTcc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/sparc64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=15000 -fno-common -I/obj/sparc64/src/sys/LINT -mcmodel=medlow -msoft-float -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/isp/../../dev/isp/isp.c FTcc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/sparc64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=15000 -fno-common -I/obj/sparc64/src/sys/LINT -mcmodel=medlow -msoft-float -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/isp/../../dev/isp/isp_target.c FT/src/sys/modules/isp/../../dev/isp/isp_target.c: In function `isp_target_notify': FT@/dev/isp/isp_inline.h:1272: warning: inlining failed in call to 'isp_get_ctio': --param large-function-growth limit reached FT/src/sys/modules/isp/../../dev/isp/isp_target.c:163: warning: called from here FT@/dev/isp/isp_inline.h:1203: warning: inlining failed in call to 'isp_get_atio2e': --param large-function-growth limit reached FT/src/sys/modules/isp/../../dev/isp/isp_target.c:168: warning: called from here FT*** Error code 1 FT FTStop in /src/sys/modules/isp. FT*** Error code 1 FT FTStop in /src/sys/modules. FT*** Error code 1 FT FTStop in /obj/sparc64/src/sys/LINT. FT*** Error code 1 FT FTStop in /src. FT*** Error code 1 FT FTStop in /src. FTTB --- 2006-02-01 16:53:26 - WARNING: /usr/bin/make returned exit code 1 FTTB --- 2006-02-01 16:53:26 - ERROR: failed to build lint kernel FTTB --- 2006-02-01 16:53:26 - tinderbox aborted FTTB --- 0.81 user 3.84 system 4174.68 real FT FT___ FT[EMAIL PROTECTED] mailing list FThttp://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 FTTo unsubscribe, send any mail to [EMAIL PROTECTED] FT FT FT ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [releng_6 tinderbox] failure on sparc64/sparc64
I've been trying to reproduce this on my local hardware, but I can't trigger it. Scott Harti Brandt wrote: This is failing since January 26. Shouldn't RELENG_6 build, especially while we're preparing a release? harti On Wed, 1 Feb 2006, FreeBSD Tinderbox wrote: FTTB --- 2006-02-01 15:43:51 - tinderbox 2.3 running on freebsd-current.sentex.ca FTTB --- 2006-02-01 15:43:51 - starting RELENG_6 tinderbox run for sparc64/sparc64 FTTB --- 2006-02-01 15:43:51 - cleaning the object tree FTTB --- 2006-02-01 15:44:16 - checking out the source tree FTTB --- 2006-02-01 15:44:16 - cd /tinderbox/RELENG_6/sparc64/sparc64 FTTB --- 2006-02-01 15:44:16 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src FTTB --- 2006-02-01 15:54:31 - building world (CFLAGS=-O -pipe) FTTB --- 2006-02-01 15:54:31 - cd /src FTTB --- 2006-02-01 15:54:31 - /usr/bin/make -B buildworld FT Rebuilding the temporary build tree FT stage 1.1: legacy release compatibility shims FT stage 1.2: bootstrap tools FT stage 2.1: cleaning up the object tree FT stage 2.2: rebuilding the object tree FT stage 2.3: build tools FT stage 3: cross tools FT stage 4.1: building includes FT stage 4.2: building libraries FT stage 4.3: make dependencies FT stage 4.4: building everything FTTB --- 2006-02-01 16:42:46 - generating LINT kernel config FTTB --- 2006-02-01 16:42:46 - cd /src/sys/sparc64/conf FTTB --- 2006-02-01 16:42:46 - /usr/bin/make -B LINT FTTB --- 2006-02-01 16:42:46 - building LINT kernel (COPTFLAGS=-O -pipe) FTTB --- 2006-02-01 16:42:46 - cd /src FTTB --- 2006-02-01 16:42:46 - /usr/bin/make buildkernel KERNCONF=LINT FT Kernel build for LINT started on Wed Feb 1 16:42:46 UTC 2006 FT stage 1: configuring the kernel FT stage 2.1: cleaning up the object tree FT stage 2.2: rebuilding the object tree FT stage 2.3: build tools FT stage 3.1: making dependencies FT stage 3.2: building everything FT[...] FT=== isp (all) FTcc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/sparc64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=15000 -fno-common -I/obj/sparc64/src/sys/LINT -mcmodel=medlow -msoft-float -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/isp/../../dev/isp/isp.c FTcc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/sparc64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=15000 -fno-common -I/obj/sparc64/src/sys/LINT -mcmodel=medlow -msoft-float -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/isp/../../dev/isp/isp_target.c FT/src/sys/modules/isp/../../dev/isp/isp_target.c: In function `isp_target_notify': FT@/dev/isp/isp_inline.h:1272: warning: inlining failed in call to 'isp_get_ctio': --param large-function-growth limit reached FT/src/sys/modules/isp/../../dev/isp/isp_target.c:163: warning: called from here FT@/dev/isp/isp_inline.h:1203: warning: inlining failed in call to 'isp_get_atio2e': --param large-function-growth limit reached FT/src/sys/modules/isp/../../dev/isp/isp_target.c:168: warning: called from here FT*** Error code 1 FT FTStop in /src/sys/modules/isp. FT*** Error code 1 FT FTStop in /src/sys/modules. FT*** Error code 1 FT FTStop in /obj/sparc64/src/sys/LINT. FT*** Error code 1 FT FTStop in /src. FT*** Error code 1 FT FTStop in /src. FTTB --- 2006-02-01 16:53:26 - WARNING: /usr/bin/make returned exit code 1 FTTB --- 2006-02-01 16:53:26 - ERROR: failed to build lint kernel FTTB --- 2006-02-01 16:53:26 - tinderbox aborted FTTB --- 0.81 user 3.84 system 4174.68 real FT FT___ FT[EMAIL PROTECTED] mailing list FThttp://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 FTTo unsubscribe, send any mail to [EMAIL PROTECTED] FT FT FT ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restartable system call behaviour
On Wed, 2006-Feb-01 11:44:08 +, Pete French wrote: I have a piece of coode which does some networking, in which I see read and write calls failing with 'Interrupted system call' from time to time. You will get EINTR if the interrupt occurs before any data is read or written. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restartable system call behaviour
Peter Jeremy wrote: On Wed, 2006-Feb-01 11:44:08 +, Pete French wrote: I have a piece of coode which does some networking, in which I see read and write calls failing with 'Interrupted system call' from time to time. You will get EINTR if the interrupt occurs before any data is read or written. Will it also happen with recv() with MSG_WAITALL flag set? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restartable system call behaviour
I have a piece of coode which does some networking, in which I see read and write calls failing with 'Interrupted system call' from time to time. You will get EINTR if the interrupt occurs before any data is read or written. Will it also happen with recv() with MSG_WAITALL flag set? Actually I have narrowed this down now, and I wwas wrong in the original posting - I was getting the EINTR returned by connect. Now I am not sure if this is correct behaviour or not - if a signal has SA_RESTART set then it should restart, but connect returns EINTR and then continues to connect in the background. I had alwways belived that if system calls are restrtable then you will never see EINTR at all. Now I dont know if this is a problem with my understanding of how the system works, or an actual bug. have filed a pr anyway, just in case it *is* a bug. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org 6.9 - Greek Keyboard Layout - FreeBSD 6.0
Giorgos Kapetanakis wrote: On Tue, January 31, 2006 12:01 am, Laganakos Vassilis wrote: Hello, I use two layouts on X, English and Greek. I use the following lines in xorg.conf to switch between those two: Option XkbRules xorg Option XkbModel acpi Option XkbLayout us,el Option XkbOptions grp:alt_shift_toggle,grp_led:scroll,altwin:menu This worked just fine until I port-upgraded to X.org 6.9 last week. It was compiled and installed correctly. Whe I tried to start X I noticed that I couldn't switch to the Greek layout, and I could not switch to to console with the Alt-Ctrl-F? key combination. When I exited the X mode, I saw the following message: The XKEYBOARD keymap compiler (xkbcomp) reports: Error:Can't find file pc/el for symbols include Exiting Abandoning symbols file basic Abandoning symbols file default Errors from xkbcomp are not fatal to the X server So I was forced to comment out the last two of those lines in xorg.conf and use only English. Greek are can be displayed in any program or Web page, but I cannot type in greek. Thanx, Vassilis It's not FreeBSD's issue, it's X.org's. The greek sybols file is no longer el, but gr. Just type: # cd /usr/X11R6/lib/X11/xkb/symbols/pc # ln -s gr el and everything should work fine ;) I had the same problem and ln -s gr el solved it. However, I looked at pc/gr and it seems it includes the pc/el file (which is now linked to pc/gr). There must be some configuration problem somewhere. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restartable system call behaviour
On Wed, Feb 01, 2006 at 08:48:30PM +, Pete French wrote: I have a piece of coode which does some networking, in which I see read and write calls failing with 'Interrupted system call' from time to time. You will get EINTR if the interrupt occurs before any data is read or written. Will it also happen with recv() with MSG_WAITALL flag set? Actually I have narrowed this down now, and I wwas wrong in the original posting - I was getting the EINTR returned by connect. Now I am not sure if this is correct behaviour or not - if a signal has SA_RESTART set then it should restart, but connect returns EINTR and then continues to connect in the background. I had alwways belived that if system calls are restrtable then you will never see EINTR at all. Now I dont know if this is a problem with my understanding of how the system works, or an actual bug. have filed a pr anyway, just in case it *is* a bug. To the best of my knowledge, connect() being always interruptable is correct and well-known. And my 4.11-STABLE system will interrupt connect() on a signal with SA_RESTART set, which disagrees with your observations yet agrees with the standard. Perhaps some logic in your software has changed since 4.11 times. Your software can poll, select, or just loop over connect() until errno != EALREADY if connect() returned EINTR. -- Yar ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [releng_6 tinderbox] failure on sparc64/sparc64
Scott Long [EMAIL PROTECTED] writes: I've been trying to reproduce this on my local hardware, but I can't trigger it. The ISP driver abuses the inline keyword. As I told mjacob earlier, the extensive inlining not only breaks the build, but probably hurts performance as well. (what gcc is complaining about, specifically, is that expanding calls to inlined functions causes isp_target_notify() to grow by more than 100%) DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
