Re: Problem with make release
Hello! On Sat, 27 Mar 1999, Scot W. Hetzel wrote: without errors. Optimization BTW do FreeBSD's team have plans to use egcs as main compiler or no? Or gcc 2.8.x at least... The FreeBSD team is looking into adding egcs into 4.0-CURRENT as the next compiler for FreeBSD. Currently, it appears to be working but hasn't been integrated into the 4.0-CURRENT source tree. Thank you :-) BTW do you know - do they going to use PentiumGCC? This compiler - the set of patches to egcs, which makes egcs able to optimize code for Pentium and above processors. As said on the homepage of PentiumGCC, there is up to 25% perfomance improvement may be when using pgcc instead of gcc and egcs. It's homepage is http://www.goof.com/pcg/ -- Yours sincerely, Vladimir Litovka, hostmaster of Sovam Teleport Kiev To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
-stable problem
Hi! Why this happens? telnet x.x.x.x nntp Trying x.x.x.x... Connected to x.x.x.x. Escape character is '^]'. assertion nsegs == 2 failed: file /usr/src/libexec/rtld-elf/map_object.c, line 158 Connection closed by foreign host. Also machine closes any connection to any port. It happens not too often, but happens. It running 3.1-STABLE. And INN 2.3-current. Dmitry. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
3com Nic Problems
Heres are the nic combinations I've tried in one machine: 3com 905 (at 100mbit) 3com 905b (at 10mbit) 3com 905b (at 100mbit) 3com 905 (at 10mbit) 3com 905 (at 100mbit) realtek 8039 (at 10mbit) 3com 905b (at 100mbit) realtek (at 10mbit) 3com 905b (at 100mbit) ne2000 (at 10mbit) In each case the 3com operating at 100mbit failed to do so smoothly. In some cases I receive device time-outs, on bootup xl0 command not completed, and in some cases no warning at all.. 100mbit will peak at 4MB/s, then all of a sudden stop, then go racing off, then stop... This doesn't happen if the 3com cards are operated by themselves. The realtek ne2000 (while slow) perform without these problems. I believe the xl? drivers have a problem. My system is 4-current (updated weekly). I only starting using 2 nics in the machine last week. (When I got my cable modem). The problem occurs both with and without natd ipfw. It also doesn't matter which of the 4 cards is receiving the data (as long as there is only one of them). Any more information needed? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3com Nic Problems
Sure enough when reading my own bug report, I found something else: xl0: 3Com 3c905B Fast Etherlink XL 10/100BaseTX rev 0x30 int a irq 9 on pci0.3.0 xl0: command never completed! xl0: Ethernet address: 00:50:04:11:5f:16 xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) xl1: 3Com 3c905 Fast Etherlink XL 10/100BaseTX rev 0x00 int a irq 12 on pci0.4.0 xl1: Ethernet address: 00:60:97:de:4e:38 xl1: autoneg complete, link status good (half-duplex, 10Mbps) xl0 should be 100mbit -- Not detected xl1 should be 10mbit -- Detected I switched the cards around, same thing happens. But with only the 100mbit network attached, it's detected fine. Thanks again for any suggestions. -Original Message- From: RT tr49...@rcc.on.ca To: curr...@freebsd.org curr...@freebsd.org Date: Sunday, March 28, 1999 1:56 PM Subject: 3com Nic Problems Heres are the nic combinations I've tried in one machine: 3com 905 (at 100mbit) 3com 905b (at 10mbit) 3com 905b (at 100mbit) 3com 905 (at 10mbit) 3com 905 (at 100mbit) realtek 8039 (at 10mbit) -= Snip =- Any more information needed? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3com Nic Problems
Of all the gin joints in all the towns in all the world, RT had to walk into mine and say: Heres are the nic combinations I've tried in one machine: 3com 905 (at 100mbit) 3com 905b (at 10mbit) 3com 905b (at 100mbit) 3com 905 (at 10mbit) 3com 905 (at 100mbit) realtek 8039 (at 10mbit) 3com 905b (at 100mbit) realtek (at 10mbit) 3com 905b (at 100mbit) ne2000 (at 10mbit) In each case the 3com operating at 100mbit failed to do so smoothly. In some cases I receive device time-outs, on bootup xl0 command not completed, Ignore the command failed to complete message. It's not fatal. It's amazing how many people get all flustered when they see this. and in some cases no warning at all.. It's timing dependent. 100mbit will peak at 4MB/s, then all of a sudden stop, then go racing off, then stop... This is a classic I didn't configure my card correctly symptom. For the Nth time, both sides of the link must use the same modes. You can't mix and match speed and duplex settings like they're tuneable parameters that you can tweak to get more performance. Both sides must match. If they can't figure out how to match on their own using autonegotiation, make them match. (You're the one with the brain and the reasoning skills after all. Well, that's the theory anyway.) If you want two 100Mbps NICs connected back to back (via crossover cable), then do the following on _both_ sides: # ifconfig xl0 media 100baseTX mediaopt full-duplex The symptoms you're describing indicate a condition where one side of the link is set for full duplex and the other is set for half. This doesn't work: when the NIC is in full duplex mode, it turns off the collision detection logic (since in theory you're not supposed to have collisions on a full duplex link). If one side is doing collision detection and the other isn't, you tend to see 'stuttery' performance. If you're connecting a NIC to a 10Mbps hub (that's hub as in repeater, not a switch), then you must set the NIC for 10Mbps half-duplex: # ifconfig xl0 media 10baseT/UTP mediaopt half-duplex If you're connecting a NIC to a 100Mbps hub (again, that's a hub as in repeater, not a switch), then you must set the NIC for 100Mbps half-duplex: # ifconfig xl0 media 100baseTX mediaopt half-duplex If you're connecting a NIC to a 100Mbps switch port, then in theory the switch port and the NIC will perform NWAY autoselection and get the modes right on their own. Sometimes this fails though, in which case you should manually configure the switch for the mode you want and configure the NIC to match. When you connect two NICs back to back and one of them supports NWAY and the other doesn't, the NIC with NWAY autonegotiation support can sometimes get the mode wrong. In this case, you should manually configure the NIC with NWAY so that agrees with the other NIC's modes using ifconfig as shown above. The NE2000 and 8039 boards don't support full duplex. So if you connect a one of these to the 3c90x NICs via crossover cable, then you must force the 3Com nic to 10Mbps half-duplex: # ifconfig xl0 media 10baseT/UTP mediaopt half-duplex This is because the NE2K and 8039 (ne2k compatible) don't support full duplex mode. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: wp...@ctr.columbia.edu | Center for Telecommunications Research Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City = It is not I who am crazy; it is I who am mad! - Ren Hoek, Space Madness = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
UPDATE4: ATA/ATAPI driver new version available.
Fourth update to the new ATA/ATAPI driver: Well, better late than newer, but things has been hectic around here, sorry for the long delay. DMA support has been added to the ATA disk driver. This only works on Intel PIIX3/4, Acer Aladdin and Promise controllers. The promise support works without the BIOS on the board, and timing modes are set to support up to UDMA speed. This solves the problems with having more than one promise controller in the same system. There is support for generic DMA, that might work on other controllers, but now you have been warned :) More chipset specific code will come soon, I have to find testers with the approbiate HW, more on that when I have it ready. The system now uses its own major numbers, please run MAKEDEV with the devices you need (ad?, acd?, afd?, ast?). For now the disk driver will also attach to the old wd major so one can at least boot without this step, but be warned, this will eventually go away. The bootblocks will have to be changed before one can boot directly from an ad device though. Fixed problems: All known hang problems should be solved The probe code has been sligthly changed, this should solve the reports I have lying around (I hope). Hangs when accessing ata atapi device on the same channel simultaniously. A real braino in ata_start caused this, fixed. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. Especially the DMA support can hose your disk real bad if anything goes wrong, agaiin you have been warned :) But please tell me how it works for you! Enjoy! -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE4: ATA/ATAPI driver new version available.
I tried this out just as soon as I saw the announcement! Your driver is really coming along well. I have three basic problems with it: 1. A hard reset is necessary to get the CD-ROM drive to work with acd. wdc0: unit 1 (atapi): NEC CD-ROM DRIVE:285/3.04, removable, dma, iordy wcd0: drive speed 2067KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked 2. My LS-120 still has no reliability with the driver, as reads are corrupted extremely often. wdc1: unit 0 (atapi): LS-120 COSM 02 UHD Floppy/0271C09T, removable, iordy wfd0: medium type unknown (no disk) 3. DMA is ineffective with file-system use. I can read from the raw device rad0 at 4.5MB/s with a 1mb block size, but when I use iozone performance is around 2.5MB/s. Mounting wd shouldn't affect that, should it? I used the same device special files to mount as before, with ATA_STATIC being used, and noticed this. Better yet, I'll try this with a corrected fstab then report back. Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re Post!: What to make of the script /usr/src/tools/LibraryReport/LibraryReport.tcl?
Hello again, Posted this a few days ago...no response... so I am trying again. Later Michael Michael E. Mercer wrote: Hello, Sorry for posting to two lists...not sure where this should go. I saw an email where someone mentioned this script... how do I make out what this script is telling me and even though this script says a library is stale, does this mean I can remove it??? Also I read someones post about the motherboard not getting enough power and causing things to run slow...how do I check if I fall into this catagory? and if I do fall into it, how do I remedy it? Thanks Michael Mercer mmer...@ipass.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE4: ATA/ATAPI driver new version available.
On Sun, 28 Mar 1999, Brian Feldman wrote: I tried this out just as soon as I saw the announcement! Your driver is really coming along well. I have three basic problems with it: 1. A hard reset is necessary to get the CD-ROM drive to work with acd. wdc0: unit 1 (atapi): NEC CD-ROM DRIVE:285/3.04, removable, dma, iordy wcd0: drive speed 2067KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked 2. My LS-120 still has no reliability with the driver, as reads are corrupted extremely often. wdc1: unit 0 (atapi): LS-120 COSM 02 UHD Floppy/0271C09T, removable, iordy wfd0: medium type unknown (no disk) 3. DMA is ineffective with file-system use. I can read from the raw device rad0 at 4.5MB/s with a 1mb block size, but when I use iozone performance is around 2.5MB/s. Mounting wd shouldn't affect that, should it? I used the same device special files to mount as before, with ATA_STATIC being used, and noticed this. Better yet, I'll try this with a corrected fstab then report back. Didn't think it would help... I corrected fstab, but the slow speed is still there. (And I notice it's time to fix my sig.) Brian Feldman _ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve!_ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE4: ATA/ATAPI driver new version available.
There seems to be an oopsie with the includes on a system without PCI in ata-dma.c: #include ata.h +#include sys/types.h + #if NATA 0 -#include pci.h #if NPCI 0 +#include pci.h #include sys/param.h #include sys/systm.h #include sys/kernel.h My 486 still spits this out tho: [...] ata0 at 0x1f0-0x1f7 irq 14 on isa [...] ad0: WDC AC2850F/28.25E40 ATA-? disk at ata0 as master ad0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=3, dmamode=1, udmamode=-1 ad0: 16 secs/int, 0 depth queue, PIO mode changing root device to wd0s1a ad0: invalid primary partition table: no magic changing root device to wd0a ad0: invalid primary partition table: no magic error 22: panic: cannot mount root (2) My PIIX3 box isn't happy with this update either: [...] ata-pci0: Intel PIIX3 IDE controller rev 0x00 on pci0.7.1 ata-pci0: Busmastering DMA supported [...] ata0 at 0x01f0 irq 14 on ata-pci0 [...] ata0: master: settting up WDMA2 mode on PIIX3/4 chip OK ad0: WDC AC22100H/11.09I14 ATA-? disk at ata0 as master ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=-1 ad0: 16 secs/int, 0 depth queue, DMA mode acd0: HITACHI CDR-8330/0007 CDROM drive at ata0 as slave acd0: drive speed 1779 - 4134KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd0s1a [...] acd0: rezero failed -- Whenever I try to mount my cdrom drive. With or without a cd in there. mount gives me mount: Input/output error I can't eject the cd tray either after I mount the drive. Its fine after boot but before I attempt to mount something. Tugrul Galatali To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
apache13-fp probs: fpsrvadm.exe core dumps.
Hello all, I am running 4.0 current and am trying to get apache13-fp to install, however the executable fpsrvadm.exe core dumps. I have tried to do this on two different 4.0 machines, same thing happens on both. Is there something I am missing? later Michael Mercer To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: apache13-fp probs: fpsrvadm.exe core dumps.
On 29-Mar-99 Michael E. Mercer wrote: Hello all, I am running 4.0 current and am trying to get apache13-fp to install, however the executable fpsrvadm.exe core dumps. I have tried to do this on two different 4.0 machines, same thing happens on both. Is there something I am missing? later Michael Mercer Yes, dg 1999/03/11 10:28:47 PST Modified files: sys/i386/confMakefile.i386 kernel.script sys/i386/include pmap.h Log: Increased kernel virtual address space to 1GB. NOTE: You MUST have fixed bootblocks in order to boot the kernel after this! Also note that this change breaks BSDI BSD/OS compatibility. Also increased default NKPT to 17 so that FreeBSD can boot on machines with =2GB of RAM. Booting on machines with exactly 4GB requires other patches, not included. Either manually back this out or use 3.1. --- Chris PiazzaAbbotsford, BC, Canada cpia...@home.net finger n...@norn.ca.eu.org for PGP key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE4: ATA/ATAPI driver new version available.
It seems Brian Feldman wrote: I tried this out just as soon as I saw the announcement! Your driver is really coming along well. I have three basic problems with it: 1. A hard reset is necessary to get the CD-ROM drive to work with acd. wdc0: unit 1 (atapi): NEC CD-ROM DRIVE:285/3.04, removable, dma, iordy wcd0: drive speed 2067KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked Ugh, one of those NEC's again, it seems there are many problems with their CDROM's, I'll try to get ahold of some... 2. My LS-120 still has no reliability with the driver, as reads are corrupted extremely often. wdc1: unit 0 (atapi): LS-120 COSM 02 UHD Floppy/0271C09T, removable, iordy wfd0: medium type unknown (no disk) Hmm, my ZIP works just fine, I'll see what I can come up with.. 3. DMA is ineffective with file-system use. I can read from the raw device rad0 at 4.5MB/s with a 1mb block size, but when I use iozone performance is around 2.5MB/s. Mounting wd shouldn't affect that, should it? I used the same device special files to mount as before, with ATA_STATIC being used, and noticed this. Better yet, I'll try this with a corrected fstab then report back. This is more likely due to the last changes Julian/Matt has committed to vfs_bio.c et all, it hoses our I/O performance pretty badly. There is work underways to fix it though. -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
