Re: Can't install R5.4
Thanks so much for your advise. It seems quite mysterious phonemonon. Anyway I will retry to install according to your advise. Nobuhiko Yoshimoto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
wine: ld-elf.so.1 not found
Hello all,
for quite some time now, wine refuses to run with the following error
message:
% wine
ELF interpreter /libexec/ld-elf.so.1 not found
zsh: 1620 abort wine
I recompiled wine a dozen times, no other app complains, and I ran make
world several times.
But the really strange part is this:
% ldd `which wine`
/usr/local/bin/wine:
ELF interpreter /libexec/ld-elf.so.1 not found
/usr/local/bin/wine: signal 6
Which means, even ldd(1) chokes at the binary. I also installed a
precompiled package for wine with the same results.
% file `which wine`
/usr/local/bin/wine: ELF 32-bit LSB executable, Intel 80386, version 1
(FreeBSD), dynamically linked (uses shared libs), stripped
% ll {,/usr}/libexec/ld*
-r-xr-xr-x 1 root wheel 136984 Jul 26 09:52 /libexec/ld-elf.so.1*
lrwxr-xr-x 1 root wheel 20 Jul 26 09:52 /usr/libexec/ld-elf.so.1@ ->
/libexec/ld-elf.so.1
% ktrace -i wine
ELF interpreter /libexec/ld-elf.so.1 not found
zsh: 1660 abort ktrace -i wine
1660 ktrace RET ktrace 0
1660 ktrace CALL execve(0xbfbfe1f0,0xbfbfe738,0xbfbfe740)
1660 ktrace NAMI "/home/q/bin/wine"
1660 ktrace RET execve -1 errno 2 No such file or directory
1660 ktrace CALL execve(0xbfbfe1f0,0xbfbfe738,0xbfbfe740)
1660 ktrace NAMI "/sbin/wine"
1660 ktrace RET execve -1 errno 2 No such file or directory
1660 ktrace CALL execve(0xbfbfe1f0,0xbfbfe738,0xbfbfe740)
1660 ktrace NAMI "/bin/wine"
1660 ktrace RET execve -1 errno 2 No such file or directory
1660 ktrace CALL execve(0xbfbfe1f0,0xbfbfe738,0xbfbfe740)
1660 ktrace NAMI "/usr/sbin/wine"
1660 ktrace RET execve -1 errno 2 No such file or directory
1660 ktrace CALL execve(0xbfbfe1f0,0xbfbfe738,0xbfbfe740)
1660 ktrace NAMI "/usr/bin/wine"
1660 ktrace RET execve -1 errno 2 No such file or directory
1660 ktrace CALL execve(0xbfbfe1f0,0xbfbfe738,0xbfbfe740)
1660 ktrace NAMI "/usr/local/sbin/wine"
1660 ktrace RET execve -1 errno 2 No such file or directory
1660 ktrace CALL execve(0xbfbfe1f0,0xbfbfe738,0xbfbfe740)
1660 ktrace NAMI "/usr/local/bin/wine"
1660 ktrace NAMI "/libexec/ld-elf.so.1"
I really can't make anything of this ... This started somewhen around
5.3 and now I'm running 6.0 with the same symptoms.
Ulrich Spoerlein
--
PGP Key ID: F0DB9F44 Encrypted mail welcome!
Fingerprint: F1CE D062 0CA9 ADE3 349B 2FE8 980A C6B5 F0DB 9F44
Ok, which part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn."
didn't you understand?
pgp0Q0LSYOjRD.pgp
Description: PGP signature
Re: em(4) stops passing data
On Tue, July 26, 2005 3:13 am, UEMURA (fka. MAENAKA) Tetsuya said: > I had had apparently same problem in April. For my time, em0 seemed dead, > though no link down message was generated, and could go up again by > `ifconfig em0 down; ifconfig em0 up'. > > My problem was caused by defected power supply which generated around > 4.5V instead of 5V, and corrected completely by replacing of power > supply. > > FYI, use physical mean when measuring voltage. Reported in BIOS or > monitor software may vary from actual. Thanks, I've tried measuring that using a multimeter. The 12v rail measures at about 12.6v, but the 5v line is only 4.9v. Is this likely to cause problems? The PSU is a brand new 450W Antec. The same PSU in a very similar system measures similar results. -- Cheers, Chris Howells -- [EMAIL PROTECTED] Web: http://www.kde.org.uk, PGP ID: 0x33795A2C KDE/Qt Developer: http://www.kde.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) stops passing data
At 09:19 AM 26/07/2005, Chris Howells wrote: Thanks, I've tried measuring that using a multimeter. The 12v rail measures at about 12.6v, but the 5v line is only 4.9v. Is this likely to cause problems? The PSU is a brand new 450W Antec. The same PSU in a very similar system measures similar results. If possible, try the version of the em driver that is in RELENG_6 or CURRENT. Not sure why the intel people didnt MFC it, but it supposedly has a number of bug fixes. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Quality of FreeBSD
On 7/26/05, J. Porter Clark <[EMAIL PROTECTED]> wrote: > >On 7/25/05, J. Porter Clark <[EMAIL PROTECTED]> wrote: > >> > >> The ATA (definitely not SATA) controller on my Dell Latitude > >> C840 laptop has READ_DMA, WRITE_DMA problems, maybe 2-3 times > >> a day unless I turn off DMA. It hangs for 3-4 seconds, logs > >> errors, then proceeds. It isn't heavily loaded. I tried using > >> Soren's ATA mkIII patches, and now it likes to panic about that > >> same frequency instead of hanging, so I'm going back to the > >> stock RELENG_5 config next chance I get. > >> > >> It's one of these: > >> > >> atapci0: port > >> 0xbfa0-0xbfaf,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 31.1 on pci0 > > >Your going back to stock RELENG_5 from what? > > RELENG_5 with Soren's patches. > > >I have that very same laptop running FreeBSD from 5.0 up to 5.4 with > >absolutely no DMA problems using it. > >Note: I did exchange the HDD from 20 to 60GB, different brands. > > Might be a clue. My laptop has this: > > ad0: 19077MB at ata0-master UDMA100 > Mine is: ad0: 57231MB [116280/16/63] at ata0-master UDMA100 > Typical errors: > Jul 23 15:00:33 auricle kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 > retries left) LBA=20586350 > Jul 25 09:01:52 auricle kernel: ad0: TIMEOUT - READ_MUL retrying (2 retries > left) LBA=1731115 > > I had been running 4.X on this box with no DMA problems until I > put 5.3 on it many months ago. It also boots Windows XP, and I > don't have any obvious disk problems with that. > I dual boot between XP and FreeBSD and even use VMWare to boot FreeBSD with the real partition. Nice having FreeBSD compiling something in the background while using XP :) > Do you have trouble with the touchpad occasionally going nuts? > I had mine replaced, and it still does it. With any OS I care > to boot. That is a keyboard problem (the pointer device in the keyboard) I had one exchanged on this C840 and 2 others on a C610. > > I have some Firewire-related problems, too, but I won't go into > them right now. I *think* I tested networking and attached storage with firewire. If you care to email me with your problems I can try see if it happens to me too. -- Joao Barros ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
setting sysctl-values with loader.conf (5.4-STABLE)
Hello, I have trouble setting sysctl-values via loader.conf on my 5.4-STABLE from 25.06.2005. This is my /boot/loader.conf: --- 8< -- snip --- # settings for xine kern.ipc.shmmax=67108864 kern.ipc.shmall=32768 # load sound module # snd_via8233_load="YES" # via8233 for ASRock K7Upgrade-880 hw.ata.atapi_dma=1 vfs.read_max=16 --- 8< --- Unfortunately the only one that gets set is hw.ata.atapi_dma=1 what should I do to set the other values and why are they not set accordingly? Changing the settings by hand after boot works without problems, though. After booting this is what I have: hw.ata.atapi_dma: 1 kern.ipc.shmmax: 33554432 kern.ipc.shmall: 8192 vfs.read_max: 8 Side note: loading snd_via8233 does work after boot on this board, but during boot it is messing up the soundchip, resulting in a loud beeping noise (it has no ogain, but wants speaker set to something different than 0). Help appreciated. Regards, Holger Kipp ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting sysctl-values with loader.conf (5.4-STABLE)
At 09:35 AM 26/07/2005, Holger Kipp wrote: Hello, I have trouble setting sysctl-values via loader.conf on my 5.4-STABLE from 25.06.2005. This is my /boot/loader.conf: --- 8< -- snip --- # settings for xine kern.ipc.shmmax=67108864 kern.ipc.shmall=32768 # load sound module # snd_via8233_load="YES" # via8233 for ASRock K7Upgrade-880 hw.ata.atapi_dma=1 vfs.read_max=16 --- 8< --- Unfortunately the only one that gets set is hw.ata.atapi_dma=1 what should I do to set the other values and why are they not set accordingly? Changing the What if you put them in /etc/sysctl.conf e.g. [hippo]% cat /etc/sysctl.conf # $FreeBSD: src/etc/sysctl.conf,v 1.8 2003/03/13 18:43:50 mux Exp $ # # This file is read when going to multi-user and its contents piped thru # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # # Uncomment this to prevent users from seeing information about processes that # are being run under another UID. #security.bsd.see_other_uids=0 vfs.read_max=16 [hippo]% ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) stops passing data
On Tue, July 26, 2005 2:23 pm, Mike Tancsa said: > If possible, try the version of the em driver that is in RELENG_6 or > CURRENT. Not sure why the intel people didnt MFC it, but it supposedly > has > a number of bug fixes. That driver seems to have too many changes to easily be backported onto RELENG_5. [1] I have however already tried the latest version of the driver (3.1.10) from the Intel web site also without success. -- Cheers, Chris Howells -- [EMAIL PROTECTED] Web: http://www.kde.org.uk, PGP ID: 0x33795A2C KDE/Qt Developer: http://www.kde.org [1]: /usr/src/sys/dev/em/if_em.c: In function `em_detach': /usr/src/sys/dev/em/if_em.c:538: warning: implicit declaration of function `if_free' /usr/src/sys/dev/em/if_em.c:538: warning: nested extern declaration of `if_free' /usr/src/sys/dev/em/if_em.c: In function `em_init_locked': /usr/src/sys/dev/em/if_em.c:844: warning: implicit declaration of function `IFP2ENADDR' /usr/src/sys/dev/em/if_em.c:844: warning: nested extern declaration of `IFP2ENADDR' /usr/src/sys/dev/em/if_em.c:845: warning: passing arg 1 of `bcopy' makes pointer from integer without a cast /usr/src/sys/dev/em/if_em.c: In function `em_print_link_status': /usr/src/sys/dev/em/if_em.c:1684: warning: implicit declaration of function `if_link_state_change' /usr/src/sys/dev/em/if_em.c:1684: warning: nested extern declaration of `if_link_state_change' /usr/src/sys/dev/em/if_em.c:1693: warning: nested extern declaration of `if_link_state_change' /usr/src/sys/dev/em/if_em.c:1684: warning: redundant redeclaration of 'if_link_state_change' /usr/src/sys/dev/em/if_em.c:1684: warning: previous implicit declaration of 'if_link_state_change' was here /usr/src/sys/dev/em/if_em.c: In function `em_setup_interface': /usr/src/sys/dev/em/if_em.c:1932: warning: implicit declaration of function `if_alloc' /usr/src/sys/dev/em/if_em.c:1932: warning: nested extern declaration of `if_alloc' /usr/src/sys/dev/em/if_em.c:1932: warning: assignment makes pointer from integer without a cast *** Error code 1 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting sysctl-values with loader.conf (5.4-STABLE)
On Tue, Jul 26, 2005 at 09:42:03AM -0400, Mike Tancsa wrote: > What if you put them in /etc/sysctl.conf Ah yes, that does work. Strange, I somehow completely missed sysctl.conf. Thank you very much - and sorry for wasting bandwidth on this. Regards, Holger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) stops passing data
> > If possible, try the version of the em driver that is in RELENG_6 or > > CURRENT. Not sure why the intel people didnt MFC it, but it supposedly > > has > > a number of bug fixes. > > That driver seems to have too many changes to easily be backported onto > RELENG_5. [1] > > I have however already tried the latest version of the driver (3.1.10) > from the Intel web site also without success. I applied the em-patch that was announced a few days ago to two servers with an Intel em-gbit-nic resetting during load. It's only been running for one day so I don't know whether my problem is gone. But so far I haven't seen any regression. The servers are connected to a Dell-switch. Applied to RELENG_5_4 and the i386- and amd64-port. regards Claus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) stops passing data
At 09:47 AM 26/07/2005, Chris Howells wrote: On Tue, July 26, 2005 2:23 pm, Mike Tancsa said: > If possible, try the version of the em driver that is in RELENG_6 or > CURRENT. Not sure why the intel people didnt MFC it, but it supposedly > has > a number of bug fixes. That driver seems to have too many changes to easily be backported onto RELENG_5. [1] Try http://people.freebsd.org/~delphij/MFC-RELENG_5/patch-em ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic on 5.4, 1 second uptime
Gavin Atkinson wrote: On Mon, 25 Jul 2005, Norberto Meijome wrote: ( This is an exact copy of my post to -questions) Hi all, I am trying to install 5.4 on a box that's been running Linux. It's a 2 year old 'Snap Appliance 4500' ( http://www.snapappliance.com/page.cfm?name=4500Main&nav=4500 ), with 4 x 120 GB EIDE, P4, 512 Mb. As soon as I try to load the kernel I get : --- (copied by hand ) Fatal trap 10: trace trap while in vm86 mode instruction pointer = 0xf000:0xf842 stack pointer= 0x0:0xff8 frame pointer = 0x0:0x0 code segment = base 0x330026, limit 0x1, type 0x9 = DPL 3, pres 1 def32 0, fram 0 processor eflags = interrupt enabled, vm86, IOPL=0 current process = 0 () trap number= 10 panic : trace trap uptime : 1 s - Every time, the same pointers / segments. This happens right after the kernel memory addresses (data? segment? pls excuse my ignorance) show after pressing an option in the boot menu. Can you boot in verbose mode and try and get a few of the lines before the lines you quoted? Knowing roughly where in the boot process this happens will probably greatly help. Hi Gavin, it dies EXACTLY before any of the boot info comes up. Step by step: - bootloader : ok - boot menu : ok - select any option (except 6, but any cmd from there that will take me attempt to boot will simply panic). - line in same gray coloured text comes up, (from memory, kernel 0x..., segment 0x etc). as soon as that finishes... - font changes to bright white. not 1 line of detection comes up, and the panic happens. I have not been able to boot any freebsd combo. tried disabling anything that I could, no luck. not even the installer. disabled acpi, DMA, safe mode, single user. zilch I hope that is something to go by. I'll take the box apart tomorrow to see what precise motherboard it is. Plan B is gentoo :( thanks for any pointers you / others can give :) Cheers, Beto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.4-stable + ipfw with dummynet = kernel panic
Hello all, Maybe you have problems with 5.4-stable (2*CPU 2.8GHz Xeon, SMP enabled) and IPFW/DUMMYNET too? With 75% probability i am geting kernel panic when i try to delete configured ipfw pipe :( best regards, Ramunas M. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Quality of FreeBSD
On Tue, Jul 26, 2005 at 02:30:49PM +0100, Joao Barros wrote: > > I dual boot between XP and FreeBSD and even use VMWare to boot FreeBSD > with the real partition. Nice having FreeBSD compiling something in > the background while using XP :) That's pretty cool... > That is a keyboard problem (the pointer device in the keyboard) I had > one exchanged on this C840 and 2 others on a C610. I'll pass that on to the maintenance guy. This is an outsourced (i.e., rented) machine. (They'd be appalled to know that it runs any non-Microsoft software. Don't nobody tell!!!) > I *think* I tested networking and attached storage with firewire. > If you care to email me with your problems I can try see if it happens > to me too. Because the hard drive is "only" 20 GB, I have an external drive connected to the IEEE 1394 port. (The USB ports on this laptop are unacceptably pokey.) Most of the problems are probably related to my attempts at hot-plugging (so to speak) this interface. The first time I connect the drive up to the box, I get this sort of thing: firewire0: New S400 device ID:0090a9506600 da0 at sbp0 bus 0 target 0 lun 0 kernel: da0: Fixed Simplified Direct Access SCSI-4 device kernel: da0: 50.000MB/s transfers kernel: da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=2, CYCLEMASTER mode kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) kernel: firewire0: bus manager 0 (me) I can then mount a partition from the drive: mount /dev/da0s2d ~/ext_bsd Sometimes I have a problem--and I can't duplicate it right now--in that if I umount the drive, then remove the plug, then reinsert it, I can't remount it immediately. Attempting to mount the drive will block for a few minutes. If I wait several minutes, it will remount immediately, or I can speed that up by removing and reinserting the plug a second time, which is what I usually do. The main problem I have is possibly related to an intermittent connection...which has been aggravated by the many insertions and reinsertions. Sometimes, out of the blue, I'll get an error like this: kernel: Interrupt storm detected on "irq11: nvidia0 cbb*"; throttling interrupt source kernel: fwohci0: BUS reset It's usually precipitated by my moving the laptop off my lap onto a table or otherwise wiggling the cable, which seems to be unpredictably sensitive. (It never happens if there is no I/O going on at the time.) I have no idea why it mentions the nvidia0 device. When this happens, any I/O on the Firewire drive will hang indefinitely. I can't fix it at that point; about all I can do is reboot. "fwcontrol -r" doesn't help any. If I reboot the system, I always have problems syncing it; it complains about unwritten buffers or vnodes, and eventually I have to manually reset it. When I come back up, I have fsck problems not only with the Firewire partitions but also /usr and others. You can say that I created the problem myself by manhandling the little plug or by even trying to insert it and remove it "hot." (Nobody said I could, nobody said I couldn't.) But I can do this with Windows XP with no problems. I also don't have any problems caused by wiggling the apparently very sensitive cable with XP. I also didn't have the wiggling-cable problem under 4.X, although it's possible that mechanical degradation since that time is at fault. (The hanging mount problem did occur under 4.X.) I haven't posted this as a bug report because (a) I haven't had much luck with bug reports and (b) I'm sure the answer would be "fix your hardware." -- J. Porter Clark <[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: FreeBSD 6.0BETA1 - Oddness with install floppies
Hi, Sorry it took me a little while to reply. I dont think this is an ATA problem as the hard disks in the system are all on SCSI channels. Anyway, I dont think an ATA timeout should affect loading the memory image from floppy, thats why I wanted to ask if anybody else had seen this. I guess I will have to download the CD and burn it to check if this is a problem with my machine, or if thats just a boot floppy issue. FYI, the system is an IBM Netfinity 7000, quad Pentium Pro box with 512meg RAM. Disks are currently attached to one of the onboard Adaptec 7800 SCSI controllers. Thanks for the reply, Alex J Burke. On 7/23/05, Matthias Buelow <[EMAIL PROTECTED]> wrote: > Alex Burke wrote: > > >I was trying to boot a system from the installation floppies, and > >after the kernel booted it dropped me out into a mountroot prompt. I > >am posative its not meant to do this, it should start sysinstall. > >I am not exactly sure what to do from here on, should i specify > >ufs:da0s1a...would that be the location of the memory disk? > > There were no ATA timeout messages? Otherwise, this would indicate > that the nasty ATA bugs are on 6.0 still. > I have (on 5.4-stable) to try a boot several times until the kernel > properly recognizes my drive, and it dumps me in the mount root > prompt when it doesn't. > > mkb. > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nfs problem
Hi, list I can't mount shared resource over nfs, when use alias on network interface: $ sudo mount_nfs 192.168.2.3:/usr/local/cvsroot /var/cvsbackup [udp] clh.cluster:/usr/local/cvsroot: NFSPROC_NULL: RPC: Timed out My config: $ cat /etc/exports /usr -alldirs -mapall=nobody $ ifconfig rl0 rl0: flags=8843 mtu 1500 options=8 inet 192.168.0.221 netmask 0xff00 broadcast 192.168.0.255 inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255 inet 192.168.2.3 netmask 0x broadcast 192.168.2.3 ether 00:00:5e:00:01:01 media: Ethernet autoselect (100baseTX ) status: active Problem in the netmask. When I try 192.168.2.1 all work fine. How I can fix the problem? By. Dmitriy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfs problem
On Jul 26, 2005, at 11:38 AM, Dmitriy Kirhlarov wrote: Problem in the netmask. When I try 192.168.2.1 all work fine. How I can fix the problem? You might have to restart portmap, and/or feed it the -h option: -h Specify specific IP addresses to bind to for UDP requests. This option may be specified multiple times and is typically necessary when running on a multi-homed host. If no -h option is speci- fied, portmap will bind to INADDR_ANY, which could lead to prob- lems on a multi-homed host due to portmap returning a UDP packet from a different IP address than it was sent to. Note that when specifying IP addresses with -h, portmap will automatically add 127.0.0.1 to the list. -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) stops passing data
On Tue, July 26, 2005 3:39 pm, Claus Guttesen said: > I applied the em-patch that was announced a few days ago to two > servers with an Intel em-gbit-nic resetting during load. It's only > been running for one day so I don't know whether my problem is gone. > But so far I haven't seen any regression. The servers are connected to > a Dell-switch. Doesn't fix the problem for me regrettably :( I can reproduce the problem within seconds of starting a large file transfers. I got the ethernet card from eBay but I've ordered a brand new one to try -- I wonder if there's any chance it could be faulty. -- Cheers, Chris Howells -- [EMAIL PROTECTED] Web: http://www.kde.org.uk, PGP ID: 0x33795A2C KDE/Qt Developer: http://www.kde.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Quality of FreeBSD
Hello list and J. :-) On Tuesday 26 July 2005 18:26, J. Porter Clark wrote: > Because the hard drive is "only" 20 GB, I have an external drive > connected to the IEEE 1394 port. (The USB ports on this laptop > are unacceptably pokey.) Most of the problems are probably > related to my attempts at hot-plugging (so to speak) this > interface. The first time I connect the drive up to the box, > I get this sort of thing: > > firewire0: New S400 device ID:0090a9506600 > da0 at sbp0 bus 0 target 0 lun 0 > kernel: da0: Fixed Simplified Direct Access SCSI-4 device > kernel: da0: 50.000MB/s transfers > kernel: da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) > fwohci0: BUS reset > fwohci0: node_id=0xc000ffc0, gen=2, CYCLEMASTER mode > kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > kernel: firewire0: bus manager 0 (me) > > I can then mount a partition from the drive: > > mount /dev/da0s2d ~/ext_bsd > > Sometimes I have a problem--and I can't duplicate it right > now--in that if I umount the drive, then remove the plug, then > reinsert it, I can't remount it immediately. Attempting to > mount the drive will block for a few minutes. If I wait several > minutes, it will remount immediately, or I can speed that up by > removing and reinserting the plug a second time, which is what I > usually do. > > The main problem I have is possibly related to an intermittent > connection...which has been aggravated by the many insertions > and reinsertions. Sometimes, out of the blue, I'll get an error > like this: > > kernel: Interrupt storm detected on "irq11: nvidia0 cbb*"; throttling interrupt source > kernel: fwohci0: BUS reset > > It's usually precipitated by my moving the laptop off my lap > onto a table or otherwise wiggling the cable, which seems to > be unpredictably sensitive. (It never happens if there is no > I/O going on at the time.) I have no idea why it mentions the > nvidia0 device. > Look at the output of `vmstat -i` and you'll probably notice the fwohci0 (or sbp(4)?) interrupt is shared with nvidia0 and other devices. > When this happens, any I/O on the Firewire drive will hang > indefinitely. I can't fix it at that point; about all I can do > is reboot. "fwcontrol -r" doesn't help any. If I reboot the > system, I always have problems syncing it; it complains about > unwritten buffers or vnodes, and eventually I have to manually > reset it. When I come back up, I have fsck problems not only > with the Firewire partitions but also /usr and others. > The sbp(4) page tells us: "If you want to force to detach the device, run ``fwcontrol -r'' several times." Have You tried that? I'm interested in your experiences with firewire mass storage, because I don't (yet) have one but might be interested in getting some extra removable HD space. I am for some reason in the belief that firewire disks might perform better than their USB-2.0 counterparts? > You can say that I created the problem myself by manhandling the > little plug or by even trying to insert it and remove it "hot." > (Nobody said I could, nobody said I couldn't.) But I can do > this with Windows XP with no problems. I also don't have any > problems caused by wiggling the apparently very sensitive cable > with XP. I also didn't have the wiggling-cable problem under > 4.X, although it's possible that mechanical degradation since > that time is at fault. (The hanging mount problem did occur > under 4.X.) I haven't posted this as a bug report because (a) I > haven't had much luck with bug reports and (b) I'm sure > the answer would be "fix your hardware." > > -- > J. Porter Clark <[EMAIL PROTECTED]> > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- marko [dot] vihoma [at] dnainternet [dot] net BOFH excuse #144: Too few computrons available ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) stops passing data
On Jul 26, 2005, at 12:03 PM, Chris Howells wrote: On Tue, July 26, 2005 3:39 pm, Claus Guttesen said: I applied the em-patch that was announced a few days ago to two servers with an Intel em-gbit-nic resetting during load. It's only been running for one day so I don't know whether my problem is gone. But so far I haven't seen any regression. The servers are connected to a Dell-switch. Doesn't fix the problem for me regrettably :( I can reproduce the problem within seconds of starting a large file transfers. I got the ethernet card from eBay but I've ordered a brand new one to try -- I wonder if there's any chance it could be faulty. I often find that if I have a cable that is less than perfect the card will seem to work but with some heavy load the switch takes the port down and it stays down until I ifconfig down & up the interface. In every instance replacing the cable takes care of the problem. -- Michael Conlen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
i386 vs amd64 - benchmark results
Hi, I've tried two benchmarks to check the speed of my system on two FreeBSD architectures i386 and amd64. I've never seen anyone posting this kind of benchmark, so here is what I found out: here the results of nbench: http://phpfi.com/71540 here is what openssl speed gives me: http://phpfi.com/71545 Sorry for posting it there, but I don't want to send attachments to this list. Please notice the memory speed penalties while the system is running on amd64 kernel. I would like to know what causes this kind of low performance when memory is being accessed. Is this a hardware problem or a problem with FreeBSD? Generally, FreeBSD-amd64 performs slightly better than FreeBSD-i386 and it's stable as expected, but I cannot find any solution to the memory problems that affect memory intensive applications as you can see. Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
need help linking??
A programmer needs your help to get his program to compile properly on freebsd. Presently he has no problems in Linux and winblows, but I could not get it running in 4.11. This is important to me because it is the strongest free chess program available and he is even giving the source! and so can be made into a port some day. Here is my message and response from him I am including the Makefile as an attachment: Hi Eriq, It refuses to link? Ask BSD users and let me know what the solution is. --- Make sure to add the appropriate include files but I don't think it would have any effect. >book.o(.text+0x83): undefined reference to `__errno_location' #include Maybe BSD has a problem with C++ notation try replacing with the obsolete #include >fen.o(.text+0x29e): undefined reference to `__strtol_internal' Not sure with strtol (try man pages) or ? >protocol.o(.text+0xd55): undefined reference to `stdin' >protocol.o(.text+0xdb1): undefined reference to `stdout' >any help you can give me is great! I have a linux binary of fruit2.1 >running on freebsd just fine but would like to compile a native binary. --- Well it looks like a linking issue specific to BSD to me. Ask in appropriate forum and let me know their answer. Fabien. # files EXE = fruit OBJS = attack.o board.o book.o eval.o fen.o hash.o list.o main.o material.o \ move.o move_check.o move_do.o move_evasion.o move_gen.o move_legal.o \ option.o pawn.o piece.o posix.o protocol.o pst.o pv.o random.o recog.o \ search.o search_full.o see.o sort.o square.o trans.o util.o value.o \ vector.o # rules all: $(EXE) .depend clean: $(RM) *.o .depend gmon.out # general CXX = g++33 CXXFLAGS = -pipe LDFLAGS = -lm # C++ CXXFLAGS += -fno-exceptions -fno-rtti # optimisation CXXFLAGS += -O3 -fstrict-aliasing CXXFLAGS += -fomit-frame-pointer # CXXFLAGS += -march=athlon-xp # SELECT ME # strip LDFLAGS += -s # dependencies $(EXE): $(OBJS) $(CXX) $(LDFLAGS) -o $@ $(OBJS) .depend: $(CXX) -MM $(OBJS:.o=.cpp) > $@ include .depend ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) stops passing data
On Tue, July 26, 2005 6:03 pm, Michael Conlen said: > I often find that if I have a cable that is less than perfect the > card will seem to work but with some heavy load the switch takes the > port down and it stays down until I ifconfig down & up the interface. > In every instance replacing the cable takes care of the problem. Ahhh. That wasn't quite the cause -- I'd already tried quite a few cat 5e cables -- but it was related to the switch. After messing around for very nearly 24 hours I've learn an important rule. Don't put a gigabit switch near, or on top of, a 1200VA UPS. Judging by the effect they have on a monitor they produce some pretty hefty electro-magnetic fields. Thanks a lot for the help all, apologies for the noise :( -- Cheers, Chris Howells -- [EMAIL PROTECTED] Web: http://www.kde.org.uk, PGP ID: 0x33795A2C KDE/Qt Developer: http://www.kde.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: need help linking??
On Tuesday, 26. July 2005 17:06, Eriq Lamar wrote: > A programmer needs your help to get his program to compile properly on > freebsd. Presently he has no problems in Linux and winblows, but I could > not get it running in 4.11. This is important to me because it is the > strongest free chess program available and he is even giving the source! > and so can be made into a port some day. [...] I just tried fruit_21_linux.zip and had no problems with linking whatsoever. There's a little compile-time glitch on 4.x due to to 4.x being overly sensitive to include-order, the attached patch fixes it. On 5.x, it compiles out of the box. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --- posix.cpp.orig Tue Jul 26 21:00:15 2005 +++ posix.cpp Tue Jul 26 21:00:35 2005 @@ -12,11 +12,11 @@ #if defined(_WIN32) || defined(_WIN64) # include #else // assume POSIX -# include // # include # include # include # include +# include #endif #include "posix.h" pgpQODvwtdS3n.pgp Description: PGP signature
Hang in NFS-mounted directory
I'm currently seeing an NFS-hang, which will probably cause me to reboot an otherwise happy system. A java process was overwriting files in an NFS-mounted directory, when I tried to Ctrl-C it (always worked before). The process is now hung in "nfrslk" state: load: 1.65 cmd: java 53499 [nfrslk] 0.07u 0.02s 0% 8956k An attempt at regular umount of the filesystem is hanging in "nfs" state: % umount /tmp/.a/beaker/host/beaker load: 1.33 cmd: umount 53521 [nfs] 0.00u 0.07s 0% 820k A subsequent attempt at forced umount is in "vfs_busy": % umount -f /tmp/.a/beaker/host/beaker load: 1.33 cmd: umount 53526 [vfs_busy] 0.00u 0.05s 0% 644k I have restarted the /etc/rc.d/nfslocking and /etc/rc.d/nfsclient -- no change. How can I help fix this problem? I'm using 5.4-STABLE as of July 7th. Thanks! -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
QLogic QLA210 OEM (Sun) Fibre Cards and FreeBSD 5.x
Has anyone here had any success getting the Sun-branded Qlogic 2Gb fibre adapters (QLA210) working under FreeBSD? Apparently these boards should work as they're compatible with the QLA2200/2300 stack (and therefore should work with the isp driver) but when booting I see the following: pcib3: at device 0.2 on pci1 pci3: on pcib3 pci3: at device 11.0 (no driver attached) I do have the ISP driver in the kernel. At the very bottom of the card it says "ISP Core", I don't know if this correlates with the name of the driver or is purely coincidental. The chip has the following numbers: QLOGIC SP212 2405465 TSA2098.1 Z0504 ZSA2098.1A Many thanks, -Eli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4.11 vs. 5.4 stablity
I am running 4.11 on a dual amd box and have found it solid as a rock for running apache2, postgres, dns and postfix. But now I am thinking of upgrading. I wonder if 5.4 is as stable for these servers that must run 24/7. And is it worth all the trouble to do, I have grown pretty lazy :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: QLogic QLA210 OEM (Sun) Fibre Cards and FreeBSD 5.x
On Tue, Jul 26, 2005 at 02:35:05PM -0700, Eli K. Breen wrote.. > Has anyone here had any success getting the Sun-branded Qlogic 2Gb fibre > adapters (QLA210) working under FreeBSD? > > Apparently these boards should work as they're compatible with the > QLA2200/2300 stack (and therefore should work with the isp driver) but > when booting I see the following: > > pcib3: at device 0.2 on pci1 > pci3: on pcib3 > pci3: at device 11.0 (no driver attached) > > I do have the ISP driver in the kernel. > > At the very bottom of the card it says "ISP Core", I don't know if this > correlates with the name of the driver or is purely coincidental. > > The chip has the following numbers: > QLOGIC > SP212 2405465 No QL number? > TSA2098.1 Z0504 > ZSA2098.1A -- Wilko Bulte [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: QLogic QLA210 OEM (Sun) Fibre Cards and FreeBSD 5.x
The board is marked QLA 210, as is the baggie, but no, this isn't listed on the chip, although I expect that to be normal. -E- Wilko Bulte wrote: On Tue, Jul 26, 2005 at 02:35:05PM -0700, Eli K. Breen wrote.. Has anyone here had any success getting the Sun-branded Qlogic 2Gb fibre adapters (QLA210) working under FreeBSD? Apparently these boards should work as they're compatible with the QLA2200/2300 stack (and therefore should work with the isp driver) but when booting I see the following: pcib3: at device 0.2 on pci1 pci3: on pcib3 pci3: at device 11.0 (no driver attached) I do have the ISP driver in the kernel. At the very bottom of the card it says "ISP Core", I don't know if this correlates with the name of the driver or is purely coincidental. The chip has the following numbers: QLOGIC SP212 2405465 No QL number? TSA2098.1 Z0504 ZSA2098.1A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: QLogic QLA210 OEM (Sun) Fibre Cards and FreeBSD 5.x
In the last episode (Jul 26), Eli K. Breen said: > Has anyone here had any success getting the Sun-branded Qlogic 2Gb fibre > adapters (QLA210) working under FreeBSD? > > Apparently these boards should work as they're compatible with the > QLA2200/2300 stack (and therefore should work with the isp driver) but > when booting I see the following: > > pcib3: at device 0.2 on pci1 > pci3: on pcib3 > pci3: at device 11.0 (no driver attached) > > I do have the ISP driver in the kernel. Adding the PCI IDs to isp_pci.c may be enough to get it working. -- Dan Nelson [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: 4.11 vs. 5.4 stablity
> I am running 4.11 on a dual amd box and have found it solid as a > rock for running apache2, postgres, dns and postfix. But now I am > thinking of upgrading. I wonder if 5.4 is as stable for these > servers that must run 24/7. And is it worth all the trouble to do, I > have grown pretty lazy :) We've been using it on dual-AthlonMP 2200+ and 2600+ systems with 3 GB RAM and 4-drive RAID5 arrays (3Ware Escalade 7506-4LP) since 5.2.1 was released. They've recently been upgraded to 5.4 (skipped 5.3 as I didn't want to re-compile all the installed ports during the school year). No problems so far, running Postfix, Amavisd-new, ClamAV, SpamAssassin, Razor, DCC, Apache, PHP4, SquirrelMail, and similar software. We're also using 5.4 on dual-Opteron 244 systems with 4 GB RAM and 4-disk RAID5 arrays (LSI MegaRAID SATA). Running Apache, MySQL, PHP4, Squid, DansGuardian, and similar. Will eventually house 12 jails to provide each school their own web/mail/proxy and content filtering server. We're also running 5.3 on 10 UP firewall boxes (ancient Compaq Deskpro P2 450 MHz systems with 512 MB RAM). No problems shoving several hundred gigabytes of data through xl and fxp interfaces all day. Haven't done any benchmarking on these systems, as we're more interested in stability and managability. We've never had any complaints about server speed -- it's always about network throughput (on the WAN side) which is outside of our control. :) If we ever get T1+ speeds into our sites, then maybe we'll look at server performance. :) -- Freddie Cash, CCNT CCLPHelpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] [EMAIL PROTECTED] [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: 4.11 vs. 5.4 stablity
Eriq wrote: > I am running 4.11 on a dual amd box and have found it solid as a rock > for running apache2, postgres, dns and postfix. But now I am thinking > of upgrading. I wonder if 5.4 is as stable for these servers that > must run 24/7. And is it worth all the trouble to do, I have grown > pretty lazy :) I'd go with that old saying, never touch a running system. 4.11 is still going to be maintained for quite a long time, so if your machine runs fine now, why not leave it as it is. If you want to upgrade, maybe you should wait a bit longer and give 6.0 a closer look (set to be released in August at the moment). My current impression is that it's stabler than 5.4 (but then, other people have reported otherwise - I suppose it's somewhat hardware-dependent). Cheers Benjamin signature.asc Description: OpenPGP digital signature
Re: em(4) stops passing data
I think 4.9V is enough for em0 to work. Your problem is likely not caused by faulty PSU. -- UEMURA (fka. MAENAKA) Tetsuya <[EMAIL PROTECTED]> Posted on Tue, 26 Jul 2005 14:19:28 +0100 (BST) by author Chris Howells <[EMAIL PROTECTED]> > > I had had apparently same problem in April. For my time, em0 seemed dead, > > though no link down message was generated, and could go up again by > > `ifconfig em0 down; ifconfig em0 up'. > > My problem was caused by defected power supply which generated around > > 4.5V instead of 5V, and corrected completely by replacing of power > > supply. > Thanks, I've tried measuring that using a multimeter. The 12v rail > measures at about 12.6v, but the 5v line is only 4.9v. Is this likely to > cause problems? The PSU is a brand new 450W Antec. The same PSU in a very > similar system measures similar results. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i386 vs amd64 - benchmark results
You might want to have a look at my private benchmarks too: http://www.alpha-tierchen.de/dateien/etc/benchmark.html Björn ___ 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 amd64/amd64
TB --- 2005-07-27 00:48:57 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-07-27 00:48:57 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2005-07-27 00:48:57 - cleaning the object tree TB --- 2005-07-27 00:49:31 - checking out the source tree TB --- 2005-07-27 00:49:31 - cd /home/tinderbox/RELENG_6/amd64/amd64 TB --- 2005-07-27 00:49:32 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2005-07-27 00:57:51 - building world (CFLAGS=-O -pipe) TB --- 2005-07-27 00:57:51 - cd /home/tinderbox/RELENG_6/amd64/amd64/src TB --- 2005-07-27 00:57:51 - /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 [...] gzip -cn /tinderbox/RELENG_6/amd64/amd64/src/share/man/man9/VFS_MOUNT.9 > VFS_MOUNT.9.gz gzip -cn /tinderbox/RELENG_6/amd64/amd64/src/share/man/man9/vfs_mount.9 > vfs_mount.9.gz gzip -cn /tinderbox/RELENG_6/amd64/amd64/src/share/man/man9/vfs_mountedon.9 > vfs_mountedon.9.gz gzip -cn /tinderbox/RELENG_6/amd64/amd64/src/share/man/man9/VFS_QUOTACTL.9 > VFS_QUOTACTL.9.gz gzip -cn /tinderbox/RELENG_6/amd64/amd64/src/share/man/man9/VFS_ROOT.9 > VFS_ROOT.9.gz gzip -cn /tinderbox/RELENG_6/amd64/amd64/src/share/man/man9/vfs_rootmountalloc.9 > vfs_rootmountalloc.9.gz gzip -cn /tinderbox/RELENG_6/amd64/amd64/src/share/man/man9/VFS_SET.9 > VFS_SET.9.gz make: don't know how to make VFS_START.9. Stop *** Error code 2 Stop in /tinderbox/RELENG_6/amd64/amd64/src/share/man. *** Error code 1 Stop in /tinderbox/RELENG_6/amd64/amd64/src/share. *** Error code 1 Stop in /tinderbox/RELENG_6/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/RELENG_6/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/RELENG_6/amd64/amd64/src. TB --- 2005-07-27 01:41:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-07-27 01:41:40 - ERROR: failed to build world TB --- 2005-07-27 01:41:40 - tinderbox aborted ___ 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 i386/i386
TB --- 2005-07-27 01:41:41 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-07-27 01:41:41 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2005-07-27 01:41:41 - cleaning the object tree TB --- 2005-07-27 01:42:07 - checking out the source tree TB --- 2005-07-27 01:42:07 - cd /home/tinderbox/RELENG_6/i386/i386 TB --- 2005-07-27 01:42:07 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2005-07-27 01:50:41 - building world (CFLAGS=-O -pipe) TB --- 2005-07-27 01:50:41 - cd /home/tinderbox/RELENG_6/i386/i386/src TB --- 2005-07-27 01:50:41 - /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 [...] gzip -cn /tinderbox/RELENG_6/i386/i386/src/share/man/man9/VFS_MOUNT.9 > VFS_MOUNT.9.gz gzip -cn /tinderbox/RELENG_6/i386/i386/src/share/man/man9/vfs_mount.9 > vfs_mount.9.gz gzip -cn /tinderbox/RELENG_6/i386/i386/src/share/man/man9/vfs_mountedon.9 > vfs_mountedon.9.gz gzip -cn /tinderbox/RELENG_6/i386/i386/src/share/man/man9/VFS_QUOTACTL.9 > VFS_QUOTACTL.9.gz gzip -cn /tinderbox/RELENG_6/i386/i386/src/share/man/man9/VFS_ROOT.9 > VFS_ROOT.9.gz gzip -cn /tinderbox/RELENG_6/i386/i386/src/share/man/man9/vfs_rootmountalloc.9 > vfs_rootmountalloc.9.gz gzip -cn /tinderbox/RELENG_6/i386/i386/src/share/man/man9/VFS_SET.9 > VFS_SET.9.gz make: don't know how to make VFS_START.9. Stop *** Error code 2 Stop in /tinderbox/RELENG_6/i386/i386/src/share/man. *** Error code 1 Stop in /tinderbox/RELENG_6/i386/i386/src/share. *** Error code 1 Stop in /tinderbox/RELENG_6/i386/i386/src. *** Error code 1 Stop in /tinderbox/RELENG_6/i386/i386/src. *** Error code 1 Stop in /tinderbox/RELENG_6/i386/i386/src. TB --- 2005-07-27 02:33:33 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-07-27 02:33:33 - ERROR: failed to build world TB --- 2005-07-27 02:33:33 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i386 vs amd64 - benchmark results
Björn König wrote: > You might want to have a look at my private benchmarks too: > > http://www.alpha-tierchen.de/dateien/etc/benchmark.html Hmmm... your benchmarks show the same effect as I have on 5.4. But I'm impressed by the RELENG_6 results. I think I'm going to upgrade my system instantly. Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] MFC em(4) 2.1.7 to RELENG_5?
On Mon, Jul 25, 2005 at 01:28:25PM +0800, Xin LI wrote: > Dear folks, > > Here is a preliminary patch that brings em(4) in RELENG_5 in sync > with RELENG_6 and HEAD (minus the softc changes): > > http://people.freebsd.org/~delphij/MFC-RELENG_5/patch-em Hi, I've just been experiencing problems on a amd64 FreeBSD 5.4-R box. It's a Dell PowerEdge 1850 box with an Intel Xeon 3.2GHz CPU, EM64T, 1GB of RAM and Intel Gigabit NICs (em driver). The last two nights it has crashed with a kernel panic at almost exactly the same time, right after starting a big bacula backup job. Attached to this email there's a kernel backtrace. The box has been running fine for about two months, and the only change I've made to it right before it started crashing was moving one of the NICs (em0) to a gigabit switch and adding a rather large client to bacula. I've also attached the last dmesg output. Do you think this patch to the em driver would help my problem? From the backtrace I can see a reference to "em_igp_cable_length_table", and from the patch I can see you are making changes to "em_igp_cable_length", so I'm hoping this problem has been addressed before. with regards, -- Morten A. Middelthon Vheech is vurse-a: ignurunce-a oor epethy? Vhu knoos? Vhu ceres? This .sig has been encheferized - http://flipp.net/bork/ kepler:/sys/amd64/compile/kepler# kgdb -q kernel.debug /var/crash/vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] #0 0x8021d30d in doadump () (kgdb) bt #0 0x8021d30d in doadump () #1 0x8021d334 in doadump () #2 0x in ?? () #3 0x8021d907 in boot () #4 0x in ?? () #5 0x803aa5df in em_igp_cable_length_table () #6 0x0031 in ?? () #7 0x2f40570a in ?? () #8 0xff003da4f780 in ?? () #9 0xff003da4f780 in ?? () #10 0x0104 in ?? () #11 0x0001 in ?? () #12 0xff003da4f780 in ?? () #13 0xff003177a000 in ?? () #14 0xff003177a000 in ?? () #15 0x8021e13f in panic () #16 0x00300010 in ?? () #17 0xa5398850 in ?? () #18 0xa5398780 in ?? () #19 0xa5398850 in ?? () #20 0xa5398790 in ?? () #21 0x803c61b2 in __func__.1 () #22 0x000c in ?? () #23 0x0007fe00 in ?? () #24 0xa5398770 in ?? () #25 0x000a in ?? () #26 0xa5398770 in ?? () #27 0x000a in ?? () #28 0x00300010 in ?? () #29 0xa53988a0 in ?? () #30 0xa53987e0 in ?? () #31 0x7a6c in ?? () #32 0x7fe89ac8 in ?? () #33 0x000c in ?? () #34 0xff003da4f701 in ?? () #35 0x000c in ?? () #36 0x0058 in ?? () #37 0x0001 in ?? () #38 0x0058b604 in ?? () #39 0x0005 in ?? () #40 0x8010 in ?? () #41 0x00575038 in ?? () #42 0x0010 in ?? () #43 0xff003da4f780 in ?? () #44 0x000c in ?? () #45 0x8035a85a in trap_fatal () #46 0x in ?? () #47 0x000f in ?? () #48 0x059b in ?? () #49 0x7fe89ac8 in ?? () #50 0x000c in ?? () #51 0xff003da4f780 in ?? () #52 0x in ?? () #53 0x in ?? () #54 0x in ?? () #55 0x8035ad52 in trap () #56 0x in ?? () #57 0xff003da4f780 in ?? () #58 0x in ?? () #59 0xff00145e2c80 in ?? () #60 0xff002d173c80 in ?? () #61 0x in ?? () #62 0x0004 in ?? () #63 0x80348e3b in calltrap () #64 0x00b4 in ?? () #65 0xff00145e2c80 in ?? () #66 0xff003da4f780 in ?? () #67 0x803ba93b in pfacts () #68 0x0058 in ?? () #69 0xff002d173c80 in ?? () #70 0x0001 in ?? () #71 0xff003da4f780 in ?? () #72 0x in ?? () #73 0x in ?? () #74 0x0001 in ?? () #75 0xff00145e2c80 in ?? () #76 0xff002d173c80 in ?? () #77 0x in ?? () #78 0x0004 in ?? () #79 0x000c in ?? () #80 0x0048 in ?? () #81 0x0004 in ?? () #82 0x in ?? () #83 0x802441c3 in turnstile_wait () #84 0x0008 in ?? () #85 0x00010093 in ?? () #86 0xa53989a0 in ?? () #87 0x0010 in ?? () #88 0x00580246 in ?? () #89 0x8052faa8 in tcbinfo () #90 0xff00145e2c82 in ?? () #91 0xff003da4f780 in ?? () #92 0x0004 in ?? () #93 0x804f6490 in inetsw () #94 0xa5398b00 in ?? () #95 0x80213adf in _mtx_lock_sleep () #96 0x in ?? () #97 0xff002e198678 in ?? () #98 0xff002e198678 in ?? () #99 0x0004 in ?? () #100 0x804f91c0 in tcp_sendspace () #101 0x802bfc77 in tcp_usr_rcvd () #102 0x0004 in ?? () #103 0xf
Re: 4.11 vs. 5.4 stablity
On Wednesday 27 July 2005 01:58, Benjamin Lutz wrote: > Eriq wrote: > > I am running 4.11 on a dual amd box and have found it solid as a rock > > for running apache2, postgres, dns and postfix. But now I am thinking > > of upgrading. I wonder if 5.4 is as stable for these servers that > > must run 24/7. And is it worth all the trouble to do, I have grown > > pretty lazy :) The bad part about an rock stable system that works flawlessly is that as an admin you do become lazy ... very lazy :). You should not change the os on the server, at least not before testing (and learning) 5.X/6.X non critical systems. -- Accuracy, n.: The vice of being right pgpSFs4z5WlJ0.pgp Description: PGP signature
