vinum trouble on 5.3-Stable
I upgraded to 5.3 on one system a while ago. And when it boots up vinum panics the system on startup with this message: panic: unmount: dangling vnode I found that if I boot in single user mode and mount / to make it rw, then start vinum, everything is fine. I just patched the kernel for the sendfile bug so this has come up again. Is this an order of execution problem? Do I change when vinum is started? What the solution. I'm happy (apart from this) with 5.x and plan to upgrade my main server to 5.x. Now that I got a good handle (I think on bind 9). Thanks, Paul. -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum trouble on 5.3-Stable
I upgraded to 5.3 on one system a while ago. And when it boots up vinum panics the system on startup with this message: panic: unmount: dangling vnode I found that if I boot in single user mode and mount / to make it rw, then start vinum, everything is fine. I just patched the kernel for the sendfile bug so this has come up again. Is this an order of execution problem? Do I change when vinum is started? What the solution. AFAIK the only current solution is to switch to gvinum. There are more details about it in the archive. I'm happy (apart from this) with 5.x and plan to upgrade my main server to 5.x. Now that I got a good handle (I think on bind 9). -- Ean Kingston E-Mail: ean_AT_hedron_DOT_org PGP KeyID: 1024D/CBC5D6BB URL: http://www.hedron.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems compiling UW imapd on 5.3-STABLE
I'm trying to get UW's imapd compiled on a 5.3-STABLE system with PAM support, as I'm trying to get imap users to authenticate to an LDAP server. It seems that I need to compile UW IMAP with PAM support to make that happen, as I then hand off auth to PAM, which then hands it off to LDAP via the PADL nss_ldap module. I get the following errors, pasted below. Seems like I need an LDFLAG or something, but I have no idea what. pop benh 22 /usr/src/source/imap-2004c1-test# make bsf SSLTYPE=none PASSWDTYPE=pam make sslnone + + Building in NON-COMPLIANCE with RFC 3501 security requirements: + Non-compliant: ++ TLS/SSL encryption is NOT supported ++ Unencrypted plaintext passwords are permitted + + In order to rectify this problem, you MUST build with: ++ SSLTYPE=nopwd + You must also have OpenSSL or equivalent installed. + Do you want to continue this build anyway? Type y or n please: y Applying an process to sources... tools/an ln -s src/c-client c-client tools/an ln -s src/ansilib c-client tools/an ln -s src/charset c-client tools/an ln -s src/osdep/unix c-client tools/an ln -s src/mtest mtest tools/an ln -s src/ipopd ipopd tools/an ln -s src/imapd imapd tools/an ln -s src/mailutil mailutil tools/an ln -s src/mlock mlock tools/an ln -s src/dmail dmail tools/an ln -s src/tmail tmail ln -s tools/an . make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=pam SSLTYPE=none IP=4 EXTRASPECIALS='' BUILDTYPE=bsf SPECIALS=GSSDIR=/usr SSLDIR=/usr SSLINCLUDE=/usr/include/openssl SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private LOCKPGM=/usr/sbin/mlock Building c-client for bsf... echo `cat SPECIALS` c-client/SPECIALS cd c-client;make bsf EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=pam SSLTYPE=none IP=4 GSSDIR=/usr SSLDIR=/usr SSLINCLUDE=/usr/include/openssl SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private LOCKPGM=/usr/sbin/mlock make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=pam SSLTYPE=none IP=4 `cat SPECIALS` OS=bsf SIGTYPE=psx CRXTYPE=nfs SPOOLDIR=/var ACTIVEFILE=/usr/local/news/lib/active RSHPATH=/usr/bin/rsh BASECFLAGS=-g -O -pipe BASELDFLAGS=-lcrypt sh -c 'rm -rf auths.c crexcl.c nfstest.c linkage.[ch] siglocal.c osdep*.[ch] *.o ARCHIVE *FLAGS *TYPE c-client.a || true' Once-only environment setup... echo cc CCTYPE echo -g -O -pipe '' CFLAGS echo -DCREATEPROTO=unixproto -DEMPTYPROTO=unixproto -DMAILSPOOL=\/var/mail\ -DANONYMOUSHOME=\/var/mail/anonymous\ -DACTIVEFILE=\/usr/local/news/lib/active\ -DNEWSSPOOL=\/var/news\ -DRSHPATH=\/usr/bin/rsh\ -DLOCKPGM=\/usr/sbin/mlock\ OSCFLAGS echo -lcrypt LDFLAGS echo ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;ranlib c-client.a ARCHIVE echo bsf OSTYPE ./drivers mbox imap nntp pop3 mh mx mbx tenex mtx mmdf unix news phile dummy ./mkauths md5 pla log echo -DMD5ENABLE=\/etc/cram-md5.pwd\ OSCFLAGS ln -s os_bsf.h osdep.h ln -s os_bsf.c osdepbas.c ln -s log_std.c osdeplog.c ln -s sig_psx.c siglocal.c ln -s crx_nfs.c crexcl.c ln -s ip4_unix.c ip_unix.c sh -c '(test -f /usr/include/sys/statvfs.h -a bsf != sc5 -a bsf != sco) ln -s nfstnew.c nfstest.c || ln -s nfstold.c nfstest.c' PAM password authentication echo -lpam -ldl LDFLAGS ln -s ckp_pam.c osdepckp.c Building without SSL support ln -s ssl_none.c osdepssl.c cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c osdep.c Building OS-dependent module If you get No such file error messages for files x509.h, ssl.h, pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL is not installed on your system. Either install OpenSSL first or build with command: make bsf SSLTYPE=none `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c `cat CCTYPE` -c `cat CFLAGS` mail.c `cat CCTYPE` -c `cat CFLAGS` misc.c `cat CCTYPE` -c `cat CFLAGS` newsrc.c `cat CCTYPE` -c `cat CFLAGS` smanager.c `cat CCTYPE` -c `cat CFLAGS` utf8.c `cat CCTYPE` -c `cat CFLAGS` siglocal.c `cat CCTYPE` -c `cat CFLAGS` dummy.c `cat CCTYPE` -c `cat CFLAGS` pseudo.c `cat CCTYPE` -c `cat CFLAGS` netmsg.c `cat CCTYPE` -c `cat CFLAGS` flstring.c `cat CCTYPE` -c `cat CFLAGS` fdstring.c `cat CCTYPE` -c `cat CFLAGS` rfc822.c `cat CCTYPE` -c `cat CFLAGS` nntp.c `cat CCTYPE` -c `cat CFLAGS` smtp.c `cat CCTYPE` -c `cat CFLAGS` imap4r1.c `cat CCTYPE` -c `cat CFLAGS` pop3.c `cat CCTYPE` -c `cat CFLAGS` unix.c `cat CCTYPE` -c `cat CFLAGS` mbx.c `cat CCTYPE` -c `cat CFLAGS` mmdf.c `cat CCTYPE` -c `cat CFLAGS` tenex.c `cat CCTYPE` -c `cat CFLAGS` mtx.c `cat CCTYPE` -c `cat CFLAGS` news.c `cat CCTYPE` -c `cat CFLAGS` phile.c `cat CCTYPE` -c `cat CFLAGS` mh.c `cat CCTYPE` -c `cat CFLAGS` mx.c sh -c 'rm -rf c-client.a || true' ar rc c
unionfs double mount reboots the system on 5.3-STABLE
I tried to build jails on top of one distribution and found the following problem. How to repeat: !WARNING: IT MAY REBOOT YOUR SYSTEM! mkdir test cd test mkdir a mkdir a-ro mkdir a-ro-rw echo a/file1 mount -v -t unionfs -o ro ~/test/a ~/test/a-ro mount -v -t unionfs -o -b ~/test/a-ro ~/test/a-ro-rw vi a-ro-rw/file1 # will reboot here mount before reboot: above:/root/test/a on /root/test/a-ro (unionfs, local, read-only, noclusterw) below:/root/test/a-ro on /root/test/a-ro-rw (unionfs, noclusterw) uname -a FreeBSD local.local.internal 5.3-STABLE FreeBSD 5.3-STABLE #14: Sat Feb 26 19:09:37 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM i386 Can anyone repeat it and let me know if you have the same result? Any suggestions what it could be? Thanks! Artem Koltsov Resource Management Wireless Facilities, Inc. Attention: Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any system and destroy any copies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: logitech cordless mouse w/ freebsd 5.3 stable
, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Sun Mar 13 08:53:16 CST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM ACPI APIC Table: AMIINT INTEL845 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.80GHz (2790.96-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf34 Stepping = 4 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 394199040 (375 MB) avail memory = 376037376 (358 MB) ioapic0 Version 2.0 irqs 0-23 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: AMIINT INTEL845 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845G (845G GMCH) SVGA controller mem 0xdff8-0xdfff,0xd000-0xd7ff irq 16 at device 2.0 on pci0 agp0: detected 8060k stolen memory agp0: aperture size is 128M uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xe400-0xe41f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xe800-0xe81f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xec00-0xec1f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 29.7 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci3: ACPI PCI bus on pcib1 pci3: display, VGA at device 5.0 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xcc00-0xccff mem 0xdfdfbf00-0xdfdfbfff irq 17 at device 10.0 on pci3 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:0b:6a:66:64:b3 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH4 UDMA100 controller port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pcm0: Intel ICH4 (82801DB) port 0xdc00-0xdc3f,0xe000-0xe0ff mem 0xdff7b900-0xdff7b9ff,0xdff7ba00-0xdff7bbff irq 17 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: Unknown AC97 Codec (id = 0x434d4983) fdc0: floppy drive controller port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: ECP parallel printer port port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse flags 0x204 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2790956669 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ad0: 38166MB WDC WD400BB-00JHA0/05.01C05 [77545/16/63] at ata0-master UDMA100 acd0: CDROM SAMSUNG CD-ROM SH-152A/C503 at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s1a % I hope all the above answered your questions Chuck and maybe gives you and others some more info :) YMMV, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: logitech cordless mouse w/ freebsd 5.3 stable
moused_port=/dev/psm0 moused_type=auto moused_enable=NO % %ps auxw | grep usbd root362 0.0 0.2 1240 780 ?? Ss5:51AM 0:00.01 /usr/sbin/usbd eric871 0.0 0.1 348 232 p3 R+7:38AM 0:00.00 grep usbd %ps auxw | grep mouse eric 1240 0.0 0.5 2276 1760 p1 RV9:18AM 0:00.00 grep mouse (csh) this seems like a waste of bandwidth but... %dmesg Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Sun Mar 13 08:53:16 CST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM ACPI APIC Table: AMIINT INTEL845 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.80GHz (2790.96-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf34 Stepping = 4 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 394199040 (375 MB) avail memory = 376037376 (358 MB) ioapic0 Version 2.0 irqs 0-23 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: AMIINT INTEL845 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845G (845G GMCH) SVGA controller mem 0xdff8-0xdfff,0xd000-0xd7ff irq 16 at device 2.0 on pci0 agp0: detected 8060k stolen memory agp0: aperture size is 128M uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xe400-0xe41f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xe800-0xe81f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xec00-0xec1f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 29.7 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci3: ACPI PCI bus on pcib1 pci3: display, VGA at device 5.0 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xcc00-0xccff mem 0xdfdfbf00-0xdfdfbfff irq 17 at device 10.0 on pci3 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:0b:6a:66:64:b3 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH4 UDMA100 controller port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pcm0: Intel ICH4 (82801DB) port 0xdc00-0xdc3f,0xe000-0xe0ff mem 0xdff7b900-0xdff7b9ff,0xdff7ba00-0xdff7bbff irq 17 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: Unknown AC97 Codec (id = 0x434d4983) fdc0: floppy drive controller port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: ECP parallel printer port port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse flags 0x204 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2790956669 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ad0: 38166MB WDC WD400BB-00JHA0/05.01C05 [77545/16/63] at ata0-master UDMA100 acd0: CDROM
Re: logitech cordless mouse w/ freebsd 5.3 stable
Chuck Robey wrote: On Mon, 14 Mar 2005, Eric wrote: I removed above this to save some bandwidth, as bandwidth is not free every where in the world :) Chuck Robey wrote: I then edit the pointer section of /etc/X11/xorg.conf to: Identifier Mouse1 Driver mouse Option ProtocolAuto Option Device /dev/bpsm0 I am running FreeBSD-6.0-current, but I bet it works for you like it works (just fine) for me. Try it, what have you got to lose? However, if it works, you owe us a usage report, Sirrah! Anyhow, FreeBSD is not terribly willing to share the mouse. When it boots, the stupid thing will start 'moused' processes on both mouses. Check this with: ps -ax | grep mouse if it's like I think it is, one of the lines that come back will report a device filename of ums0. You need this process dead, dead, dead. You *could*, I suppose, edit /etc/usbd.conf ... After you do that, the stuff you have above for Xorg isn't enough either, cause you left out the wheel. take those lines out and replace them with Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/ums0 Option Buttons 5 Option ZAxisMapping 4 5 EndSection Don't forget, at the top: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Try this, tell me how it works. Chuck, Setting my mouse driver to ums0, will make X crash before loading. My box never reported the ums0 device/the usb mouse. The usbd is running. There is no moused processes running on this box, as it is disabled in /etc/rc.conf. I get the scroll wheel to work as a middle button, but you are right, the scroll feature does not work. Just 1 thing I need to confirm: did you kill the moused process BEFORE starting X? Because if you didn't, that's exactly what happens to me. I need to kill the moused process that is tying up ums0, then I can start up X. I do not have any problem with the moused running at all (after doing the steps in the original email). Also as far as my os is concerned there is no USB mouse attached to the workstation. We are using different versions of FreeBSD :) By editing /etc/rc.conf and adding this line at the end: moused_enable=NO , and then rebooting, keeps my moused from starting. I suppose I could have done #killall -9 moused *and* edited /etc/rc.conf with no immediate reboot. When I appended the line to /boot/device.hints, I rebooted for that too. This box is a workstation with one user, me, so uptime is not a issue. As far as the order of the steps, please see the original email. I did start X last after doing everything in the original email, as the mouse did not work at all until all steps were complete. Option Buttons 5 Option ZAxisMapping 4 5 Setting those two options does not enable the scroll wheel. I think that is due to the generic PS/2 driver reported in dmesg. Having a working scroll wheel was never a issue for me :) Also note, I never tried FreeBSD 6.x . No, let's fix the mouse first, then we worry about the mouse wheel. I re-read man psm and I believe the flags i set (/boot/device.hints) keep the mouse driver at level 0. A level 1 driver would make the scroll wheel work. When I boot with a level 1 driver, my mouse is completly dead in X. It is beyond my skills and desire, to code a custom driver :) I am not sure if the following info matters or not: This is included as it may give you some hints for fixing the wheel feature. This mouse config was a combination of some google hints that led me to look at, 'man psm', 'man device.hints', and my experience with Freebsd 4.x. FreeBSD 4.x taught me that using /dev/bpsm0 in the X config would work, with this mouse and this kvm. I didn't try setting up the moused in /etc/rc.conf with FreeBSD 5.x. In FreeBSD 4.x adding the bpsm0 config to /etc/rc.conf just lead to error messages getting reported to my shells every so often. Here is some additional info: %ls /dev acd0ata fidopsm0ttyv3 acpiatkbd0 geom.ctlptyp0 ttyv4 ad0 audio0.0io ptyp1 ttyv5 ad0s1 audio0.1kbd0ptyp2 ttyv6 ad0s10 bpf0klogptyp3 ttyv7 ad0s1a bpsm0 kmemrandom ttyv8 ad0s1b console log sndstat ttyv9 ad0s1c consolectl lpt0stderr ttyva ad0s1d cttylpt0.ctlstdin ttyvb ad0s1e cuaa0 mdctl stdout ttyvc ad0s1f cuaia0 mem sysmousettyvd ad0s2 cuala0 mixer0 ttyd0 ttyve ad0s3
Re: logitech cordless mouse w/ freebsd 5.3 stable
My ugly mouse hack: I am sure this question has already been answered, although I couldn't find the answer via google. Hardware and Software: Logitech USB cordless mouse M/N:M-RN67 P/N:851390- w/ ps/2 adapter Auravision slimseries ps/2 keyboard /w wire a starband kvm switch, 4 port PS/2 for both keyboard and mouse w/ extern power source. FreeBSD 5.3 stable cpu=2.8 cel Using the ps/2 adapter with my mouse, was required to use the kvm. dmesg reports this for my mouse by default: psm0: PS/2 Mouse flags 0x24 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 the mouse will not work. appending: hint.psm.0.flags=0x204 to /boot/device.hints I now get this via dmesg: psm0: PS/2 Mouse flags 0x204 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 I then edited /etc/rc.conf and disabled my console mouse (moused) (which I would prefere worked) moused_enable=NO I then edit the pointer section of /etc/X11/xorg.conf to: Identifier Mouse1 Driver mouse Option ProtocolAuto Option Device /dev/bpsm0 notice that is the b psm device that i am using which is for blocking mode or bpsm At any rate, the mouse now works in X, through the kvm, and through usb to ps/2 adapter. I hope this helps someone else :) YMMV, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: logitech cordless mouse w/ freebsd 5.3 stable
On Sun, 13 Mar 2005, Eric wrote: My ugly mouse hack: I am sure this question has already been answered, although I couldn't find the answer via google. Hardware and Software: Logitech USB cordless mouse M/N:M-RN67 P/N:851390- w/ ps/2 adapter Auravision slimseries ps/2 keyboard /w wire a starband kvm switch, 4 port PS/2 for both keyboard and mouse w/ extern power source. FreeBSD 5.3 stable cpu=2.8 cel Using the ps/2 adapter with my mouse, was required to use the kvm. dmesg reports this for my mouse by default: psm0: PS/2 Mouse flags 0x24 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 the mouse will not work. appending: hint.psm.0.flags=0x204 to /boot/device.hints I now get this via dmesg: psm0: PS/2 Mouse flags 0x204 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 I then edited /etc/rc.conf and disabled my console mouse (moused) (which I would prefere worked) moused_enable=NO I then edit the pointer section of /etc/X11/xorg.conf to: Identifier Mouse1 Driver mouse Option ProtocolAuto Option Device /dev/bpsm0 I am running FreeBSD-6.0-current, but I bet it works for you like it works (just fine) for me. Try it, what have you got to lose? However, if it works, you owe us a usage report, Sirrah! Anyhow, FreeBSD is not terribly willing to share the mouse. When it boots, the stupid thing will start 'moused' processes on both mouses. Check this with: ps -ax | grep mouse if it's like I think it is, one of the lines that come back will report a device filename of ums0. You need this process dead, dead, dead. You *could*, I suppose, edit /etc/usbd.conf ... After you do that, the stuff you have above for Xorg isn't enough either, cause you left out the wheel. take those lines out and replace them with Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/ums0 Option Buttons 5 Option ZAxisMapping 4 5 EndSection Don't forget, at the top: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Try this, tell me how it works. notice that is the b psm device that i am using which is for blocking mode or bpsm At any rate, the mouse now works in X, through the kvm, and through usb to ps/2 adapter. I hope this helps someone else :) YMMV, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: logitech cordless mouse w/ freebsd 5.3 stable
Eric, Please submit this via the send-pr mechanism so that it will get fixed in the next version of FreeBSD. thanks, Ted [EMAIL PROTECTED] wrote: My ugly mouse hack: I am sure this question has already been answered, although I couldn't find the answer via google. Hardware and Software: Logitech USB cordless mouse M/N:M-RN67 P/N:851390- w/ ps/2 adapter Auravision slimseries ps/2 keyboard /w wire a starband kvm switch, 4 port PS/2 for both keyboard and mouse w/ extern power source. FreeBSD 5.3 stable cpu=2.8 cel Using the ps/2 adapter with my mouse, was required to use the kvm. dmesg reports this for my mouse by default: psm0: PS/2 Mouse flags 0x24 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 the mouse will not work. appending: hint.psm.0.flags=0x204 to /boot/device.hints I now get this via dmesg: psm0: PS/2 Mouse flags 0x204 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 I then edited /etc/rc.conf and disabled my console mouse (moused) (which I would prefere worked) moused_enable=NO I then edit the pointer section of /etc/X11/xorg.conf to: Identifier Mouse1 Driver mouse Option ProtocolAuto Option Device /dev/bpsm0 notice that is the b psm device that i am using which is for blocking mode or bpsm At any rate, the mouse now works in X, through the kvm, and through usb to ps/2 adapter. I hope this helps someone else :) YMMV, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange load averages on 5.3-STABLE
Dmitry Kozhevnikov wrote: please show us 1. cat /var/run/dmesg.boot 2. uname -a 3. egrep (^REVISION|^BRANCH) /usr/src/sys/conf/newvers.sh GPT David Fleck wrote: On Thu, 10 Mar 2005, Michael Ross wrote: last pid: 771; load averages: 176.65, 770.13, 926.55 up 0+00:03:13 08:11:07 Your may have compiled kernel and userland from different sources. and programs like ps(1) and top(1) will fail to work until the kernel and source code versions are the same. from the handbook is what comes to my mind. GPT I've compiled from the same source. I've also seen ridiculously-high load numbers when NFS-mounted filesystems are inaccessible. Usually that degrades system performance, though. GPT It's strange because everything is working fine and I don't use NFS on GPT it. For example, the load hits 900 and suddenly it's 3. # uname -a FreeBSD srv-02.bs2.local 5.3-STABLE FreeBSD 5.3-STABLE #6: Mon Feb 14 09:32:36 BRST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SRV-02-LOCAL i386 # egrep (^REVISION|^BRANCH) /usr/src/sys/conf/newvers.sh REVISION=5.3 BRANCH=STABLE # cat /var/run/dmesg.boot Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #6: Mon Feb 14 09:32:36 BRST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SRV-02-LOCAL ACPI APIC Table: IntelR AWRDACPI Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.26GHz (2261.01-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf25 Stepping = 5 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 268369920 (255 MB) avail memory = 257159168 (245 MB) ioapic0 Version 2.0 irqs 0-23 on motherboard netsmb_dev: loaded npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: IntelR AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82865 host to AGP bridge mem 0xf000-0xf7ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 rl0: RealTek 8139 10/100BaseTX port 0xb000-0xb0ff mem 0xfa00-0xfaff irq 20 at device 2.0 on pci2 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:7d:d7:e0:5f rl1: RealTek 8139 10/100BaseTX port 0xb400-0xb4ff mem 0xfa001000-0xfa0010ff irq 23 at device 9.0 on pci2 miibus1: MII bus on rl1 rlphy1: RealTek internal media interface on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: Ethernet address: 00:0d:87:47:56:a0 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_tz0: Thermal Zone on acpi0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: ISA Option ROM at iomem 0xc-0xc on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2261014504 Hz quality 800 Timecounters tick every 10.000 msec ad0: 38204MB SAMSUNG SP0411N/TW100-11 [77622/16/63] at ata0-master UDMA100 ad2: 38166MB ST340014A/8.01 [77545/16/63] at ata1-master UDMA100 Mounting root from ufs:/dev/ad0s1a -- Giovanni PS.: Please CC me as I'm not on this list. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: Strange load averages on 5.3-STABLE
Sometimes I get strange effects on 5.3-STABLE too. So I use tag=RELENG_5_3 and have no such troubles. Try this, maybe sources was broken a little that time? GPT Dmitry Kozhevnikov wrote: please show us 1. cat /var/run/dmesg.boot 2. uname -a 3. egrep (^REVISION|^BRANCH) /usr/src/sys/conf/newvers.sh GPT David Fleck wrote: On Thu, 10 Mar 2005, Michael Ross wrote: last pid: 771; load averages: 176.65, 770.13, 926.55 up 0+00:03:13 08:11:07 Your may have compiled kernel and userland from different sources. and programs like ps(1) and top(1) will fail to work until the kernel and source code versions are the same. from the handbook is what comes to my mind. GPT I've compiled from the same source. I've also seen ridiculously-high load numbers when NFS-mounted filesystems are inaccessible. Usually that degrades system performance, though. GPT It's strange because everything is working fine and I don't use NFS on GPT it. For example, the load hits 900 and suddenly it's 3. GPT # uname -a GPT FreeBSD srv-02.bs2.local 5.3-STABLE FreeBSD 5.3-STABLE #6: Mon Feb 14 GPT 09:32:36 BRST 2005 GPT [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SRV-02-LOCAL i386 GPT # egrep (^REVISION|^BRANCH) /usr/src/sys/conf/newvers.sh GPT REVISION=5.3 GPT BRANCH=STABLE GPT # cat /var/run/dmesg.boot GPT Copyright (c) 1992-2005 The FreeBSD Project. GPT Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 GPT The Regents of the University of California. All rights reserved. GPT FreeBSD 5.3-STABLE #6: Mon Feb 14 09:32:36 BRST 2005 GPT [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SRV-02-LOCAL GPT ACPI APIC Table: IntelR AWRDACPI GPT Timecounter i8254 frequency 1193182 Hz quality 0 GPT CPU: Intel(R) Pentium(R) 4 CPU 2.26GHz (2261.01-MHz 686-class CPU) GPTOrigin = GenuineIntel Id = 0xf25 Stepping = 5 GPT Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE GPT real memory = 268369920 (255 MB) GPT avail memory = 257159168 (245 MB) GPT ioapic0 Version 2.0 irqs 0-23 on motherboard GPT netsmb_dev: loaded GPT npx0: [FAST] GPT npx0: math processor on motherboard GPT npx0: INT 16 interface GPT acpi0: IntelR AWRDACPI on motherboard GPT acpi0: Power Button (fixed) GPT Timecounter ACPI-fast frequency 3579545 Hz quality 1000 GPT acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 GPT cpu0: ACPI CPU on acpi0 GPT acpi_button0: Power Button on acpi0 GPT acpi_button1: Sleep Button on acpi0 GPT pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 GPT pci0: ACPI PCI bus on pcib0 GPT agp0: Intel 82865 host to AGP bridge mem 0xf000-0xf7ff at GPT device 0.0 on pci0 GPT pcib1: PCI-PCI bridge at device 1.0 on pci0 GPT pci1: PCI bus on pcib1 GPT pci1: display, VGA at device 0.0 (no driver attached) GPT pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 GPT pci2: ACPI PCI bus on pcib2 GPT rl0: RealTek 8139 10/100BaseTX port 0xb000-0xb0ff mem GPT 0xfa00-0xfaff irq 20 at device 2.0 on pci2 GPT miibus0: MII bus on rl0 GPT rlphy0: RealTek internal media interface on miibus0 GPT rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto GPT rl0: Ethernet address: 00:e0:7d:d7:e0:5f GPT rl1: RealTek 8139 10/100BaseTX port 0xb400-0xb4ff mem GPT 0xfa001000-0xfa0010ff irq 23 at device 9.0 on pci2 GPT miibus1: MII bus on rl1 GPT rlphy1: RealTek internal media interface on miibus1 GPT rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto GPT rl1: Ethernet address: 00:0d:87:47:56:a0 GPT isab0: PCI-ISA bridge at device 31.0 on pci0 GPT isa0: ISA bus on isab0 GPT atapci0: Intel ICH5 UDMA100 controller port GPT 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 GPT ata0: channel #0 on atapci0 GPT ata1: channel #1 on atapci0 GPT pci0: serial bus, SMBus at device 31.3 (no driver attached) GPT acpi_tz0: Thermal Zone on acpi0 GPT sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on GPT acpi0 GPT sio0: type 16550A GPT orm0: ISA Option ROM at iomem 0xc-0xc on isa0 GPT pmtimer0 on isa0 GPT atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 GPT atkbd0: AT Keyboard irq 1 on atkbdc0 GPT kbd0 at atkbd0 GPT atkbd0: [GIANT-LOCKED] GPT sc0: System console at flags 0x100 on isa0 GPT sc0: VGA 16 virtual consoles, flags=0x300 GPT sio1: configured irq 3 not in bitmap of probed irqs 0 GPT sio1: port may not be enabled GPT vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 GPT Timecounter TSC frequency 2261014504 Hz quality 800 GPT Timecounters tick every 10.000 msec GPT ad0: 38204MB SAMSUNG SP0411N/TW100-11 [77622/16/63] at ata0-master UDMA100 GPT ad2: 38166MB ST340014A/8.01 [77545/16/63] at ata1-master UDMA100 GPT Mounting root from ufs:/dev/ad0s1a ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions
Strange load averages on 5.3-STABLE
Hi, This is the output of top: last pid: 771; load averages: 176.65, 770.13, 926.55 up 0+00:03:13 08:11:07 48 processes: 1 running, 47 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 40M Active, 63M Inact, 45M Wired, 16K Cache, 35M Buf, 99M Free Swap: 487M Total, 487M Free PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 622 mysql 200 58104K 28040K kserel 0:01 0.64% 0.63% mysqld 587 root 960 16888K 10592K select 0:00 0.00% 0.00% httpd 652 root 960 6252K 4536K select 0:00 0.00% 0.00% snmpd [...] Strange uh ? The system seems normal besides that. I only saw that because sendmail stopped aceppting connections because of the high load. FreeBSD 5.3-STABLE #6: Mon Feb 14 09:32:36 BRST 2005 -- Giovanni PS.: Please CC: me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange load averages on 5.3-STABLE
On Thu, 10 Mar 2005 08:13:53 -0300 Giovanni P. Tirloni [EMAIL PROTECTED] wrote: Hi, This is the output of top: last pid: 771; load averages: 176.65, 770.13, 926.55 up 0+00:03:13 08:11:07 48 processes: 1 running, 47 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 40M Active, 63M Inact, 45M Wired, 16K Cache, 35M Buf, 99M Free Swap: 487M Total, 487M Free PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 622 mysql 200 58104K 28040K kserel 0:01 0.64% 0.63% mysqld 587 root 960 16888K 10592K select 0:00 0.00% 0.00% httpd 652 root 960 6252K 4536K select 0:00 0.00% 0.00% snmpd [...] Your may have compiled kernel and userland from different sources. and programs like ps(1) and top(1) will fail to work until the kernel and source code versions are the same. from the handbook is what comes to my mind. Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange load averages on 5.3-STABLE
On Thu, 10 Mar 2005, Michael Ross wrote: last pid: 771; load averages: 176.65, 770.13, 926.55 up 0+00:03:13 08:11:07 Your may have compiled kernel and userland from different sources. and programs like ps(1) and top(1) will fail to work until the kernel and source code versions are the same. from the handbook is what comes to my mind. I've also seen ridiculously-high load numbers when NFS-mounted filesystems are inaccessible. Usually that degrades system performance, though. -- David Fleck [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange load averages on 5.3-STABLE
David Fleck wrote: On Thu, 10 Mar 2005, Michael Ross wrote: last pid: 771; load averages: 176.65, 770.13, 926.55 up 0+00:03:13 08:11:07 Your may have compiled kernel and userland from different sources. and programs like ps(1) and top(1) will fail to work until the kernel and source code versions are the same. from the handbook is what comes to my mind. I've compiled from the same source. I've also seen ridiculously-high load numbers when NFS-mounted filesystems are inaccessible. Usually that degrades system performance, though. It's strange because everything is working fine and I don't use NFS on it. For example, the load hits 900 and suddenly it's 3. -- Giovanni ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: Strange load averages on 5.3-STABLE
please show us 1. cat /var/run/dmesg.boot 2. uname -a 3. egrep (^REVISION|^BRANCH) /usr/src/sys/conf/newvers.sh GPT David Fleck wrote: On Thu, 10 Mar 2005, Michael Ross wrote: last pid: 771; load averages: 176.65, 770.13, 926.55 up 0+00:03:13 08:11:07 Your may have compiled kernel and userland from different sources. and programs like ps(1) and top(1) will fail to work until the kernel and source code versions are the same. from the handbook is what comes to my mind. GPT I've compiled from the same source. I've also seen ridiculously-high load numbers when NFS-mounted filesystems are inaccessible. Usually that degrades system performance, though. GPT It's strange because everything is working fine and I don't use NFS on GPT it. For example, the load hits 900 and suddenly it's 3. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with libgphoto2, Canon Ixus v2 (USB) and 5.3-STABLE
Chris Hill wrote: On Sun, 6 Mar 2005, Roland Smith wrote: On Sun, Mar 06, 2005 at 07:48:16PM +0100, Olivier Certner wrote: I've tried to download a few pics from my Canon Ixus v2 camera with libgphoto2 (frontends: kamera and gphoto2) without success. The camera is supported though, I even used libgphoto2 successfully on a Linux system with an older version of the lib (which I don't remember!). In dealing with digital cameras, I've always found it easier to try and mount them as a USB drive (via umass / da), which a lot of them support. If you hook up the camera, is there any mention of a umass device in dmesg? If so you can just mount it as a harddisk. Thanks. As far as I know, my Canons D-30 and A80 do not work as umass storage devices, so I need gphoto2 software in order to get the pictures :-( Ramiro. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with libgphoto2, Canon Ixus v2 (USB) and 5.3-STABLE
Hi there, I've tried to download a few pics from my Canon Ixus v2 camera with libgphoto2 (frontends: kamera and gphoto2) without success. The camera is supported though, I even used libgphoto2 successfully on a Linux system with an older version of the lib (which I don't remember!). I've tried to add several traces to libgphoto2 to see where the problem was happening. I get as deep as usb_bulk_read but I haven't investigated further at the moment. libusb, libgphoto2 and gphoto2 have all been compiled from the ports collection, one time with and the other time without optimization flags, leading to the same result. Below is the output of gphoto2 --debug -l, in which there are some extra traces left (beginning with Olivier:). I see a strange 'Canon:PowerShot S200' at some point, but have not made anything of that. I've no special tweaks for usb. FreeBSD version is 5.3-STABLE, compiled with the following for usb (in case it would help): # USB support device uhci# UHCI PCI-USB interface #device ohci# OHCI PCI-USB interface device usb # USB Bus (required) #device udbp# USB Double Bulk Pipe devices device ugen# Generic device uhid# Human Interface Devices device ukbd# Keyboard device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse #device urio# Diamond Rio 500 MP3 player #device uscanner# Scanners Feel free to ask if you would like more information! Thanks for reading. Regards, Olivier PS: This post has been submitted to both the freebsd-questions and gphoto-devel mailing lists because it might interest both. No follow-up nor reply to! 0.33 main(2): ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST: 0.001896 main(2): gphoto2 2.1.5 0.002171 main(2): gphoto2 has been compiled with the following options: 0.002470 main(2): + cc (C compiler used) 0.002728 main(2): + popt (for handling command-line parameters) 0.003014 main(2): + exif (for displaying EXIF information) 0.003292 main(2): + no cdk (for accessing configuration options) 0.003579 main(2): + aa (for displaying live previews) 0.003852 main(2): + jpeg (for displaying live previews in JPEG format) 0.004147 main(2): + readline (for easy navigation in the shell) 0.004443 main(2): libgphoto2 2.1.5 0.004698 main(2): libgphoto2 has been compiled with the following options: 0.004996 main(2): + cc (C compiler used) 0.005254 main(2): + EXIF (for special handling of EXIF files) 0.005537 main(2): + no ltdl (working around buggy libltdl, eh? :-) 0.005846 main(2): + no /proc/meminfo (adapts cache size to memory available) 0.006158 main(2): libgphoto2_port 0.5.1 0.006420 main(2): libgphoto2_port has been compiled with the following options: 0.006723 main(2): + cc (C compiler used) 0.007058 main(2): + USB (for USB cameras) 0.007319 main(2): + serial (for serial cameras) 0.007582 main(2): + no resmgr (serial port access and locking) 0.007864 main(2): + no baudboy (serial port locking) 0.008131 main(2): + no ttylock (serial port locking) 0.008403 main(2): + no lockdev (serial port locking) 0.008669 main(2): + no ltdl (working around buggy libltdl, eh? :-) 0.009132 main(2): The user has not specified both a model and a port. Try to figure them out. 0.009496 gp-port-info-list(2): Loading io-drivers from '/usr/local/lib/gphoto2_port/0.5.1'... 0.010304 gphoto2-port-serial(2): Trying to lock '/dev/cuaa0'... 0.013833 gphoto2-port-serial(2): Trying to lock '/dev/cuaa1'... 0.014186 gphoto2-port-serial(2): Trying to lock '/dev/cuaa2'... 0.014505 gphoto2-port-serial(2): Trying to lock '/dev/cuaa3'... 0.014822 gphoto2-port-serial(2): Trying to lock '/dev/cuaa4'... 0.015138 gphoto2-port-serial(2): Trying to lock '/dev/cuaa5'... 0.015456 gphoto2-port-serial(2): Trying to lock '/dev/cuaa6'... 0.015771 gphoto2-port-serial(2): Trying to lock '/dev/cuaa7'... 0.016088 gphoto2-port-serial(2): Trying to lock '/dev/cuaa8'... 0.016406 gphoto2-port-serial(2): Trying to lock '/dev/cuaa9'... 0.016725 gphoto2-port-serial(2): Trying to lock '/dev/cuaaa'... 0.017041 gphoto2-port-serial(2): Trying to lock '/dev/cuaab'... 0.017360 gphoto2-port-serial(2): Trying to lock '/dev/cuaac'... 0.017676 gphoto2-port-serial(2): Trying to lock '/dev/cuaad'... 0.017992 gphoto2-port-serial(2): Trying to lock '/dev/cuaae'... 0.018307 gphoto2-port-serial(2): Trying to lock '/dev/cuaaf'... 0.019431 gphoto2-port-core(2): Loaded '' (^serial) from 'libgphoto2_port_serial.so' 0.042286 gphoto2-port-core(2): Loaded 'Universal Serial Bus' (usb:) from 'libgphoto2_port_usb.so' 0.042929 gphoto2-port-core(2): Loaded 'Universal Serial Bus' (usb:/dev/usb1,/dev/ugen0
Re: Problem with libgphoto2, Canon Ixus v2 (USB) and 5.3-STABLE
Hello Olivier I have a Canon D-30 that works out of the box with gphoto2. Just #gphoto2 -P is enough for downloading the pictures. But I have a Canon A80 that refuses to do it without commandline tweaking. #gphoto2 --camera Canon PowerShot A80 (PTP) --port usb: -P If I use the simple command gphoto2 -P with the A80 it fails and I have to restart the computer again to make it work (cause it fails to recognice any usb device). So, I suggest you to to try this command as root: #gphoto2 --camera Canon Digital IXUS v2 --port usb: -P You can list supported cameras with #gphoto2 --list-cameras and try . Tell us your experience. Ramiro. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with libgphoto2, Canon Ixus v2 (USB) and 5.3-STABLE
On Sun, Mar 06, 2005 at 07:48:16PM +0100, Olivier Certner wrote: Hi there, I've tried to download a few pics from my Canon Ixus v2 camera with libgphoto2 (frontends: kamera and gphoto2) without success. The camera is supported though, I even used libgphoto2 successfully on a Linux system with an older version of the lib (which I don't remember!). In dealing with digital cameras, I've always found it easier to try and mount them as a USB drive (via umass / da), which a lot of them support. If you hook up the camera, is there any mention of a umass device in dmesg? If so you can just mount it as a harddisk. Another option is a memory card reader that you can mount as a drive. Roland -- R.F. Smith /\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \Respect for open standards pgpQlYxqeT7pJ.pgp Description: PGP signature
Re: Problem with libgphoto2, Canon Ixus v2 (USB) and 5.3-STABLE
On Sun, 6 Mar 2005, Roland Smith wrote: On Sun, Mar 06, 2005 at 07:48:16PM +0100, Olivier Certner wrote: I've tried to download a few pics from my Canon Ixus v2 camera with libgphoto2 (frontends: kamera and gphoto2) without success. The camera is supported though, I even used libgphoto2 successfully on a Linux system with an older version of the lib (which I don't remember!). In dealing with digital cameras, I've always found it easier to try and mount them as a USB drive (via umass / da), which a lot of them support. If you hook up the camera, is there any mention of a umass device in dmesg? If so you can just mount it as a harddisk. Agreed. I've never even attempted to use gphoto or anything like it. I just plug in the USB cable and copy files from the camera. Quick and easy, no special software needed. Once the pictures are off the camera, you can have your evil way with them :^) Another nice thing is that I can cd to the directory on the camera's drive where the pictures are stored, and manipulate them from a shell prompt, instead of having to deal with the camera's menu buttons. To make life easier, I have an entry in /etc/fstab: /dev/da0s1 /camera msdos rw,noauto 0 0 ...and a symlink: lrwxr-xr-x 1 chris chris 21 Mar 6 16:59 camera - /camera/dcim/101msdcf (this is for a Sony camera, but you get the idea.) -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange IP problem with 5.3 STABLE #2
Hello. We have a Dell PE 1850 (dual Intel PRO/1000 nics, em driver) running FreeBSD 5.3 STABLE #2. The generic kernel has been configured to include IPFW and SMP as follows: options IPFIREWALL options IPFIREWALL_VERBOSE options IPDIVERT options SMP No other changes have been made. The firewall options in rc.conf are as follows: firewall_enable=YES firewall_type=OPEN firewall_quiet=NO The problem is that some IP addresses on our class C subnet do not work. I mean the NIC can be configured to use the IP address and it shows up in ifconfig output, but the system cannot be pinged or otherwise accessed from outside the subnet. Within the subnet it is fine. The only other reference I have found to a similar issue is one involving VLANs http://lists.freebsd.org/pipermail/freebsd-current/2004-November/042591.html but I think my problem is different as I am not configuring any VLANs. Also rebooting the system makes no difference. I had been using the RELENG_5_3 branch and run into this problem. I switched to RELENG_5, rebuilt the system, and the IPs that were giving me problems started working. Now, however, I have found another one that does not work. I am running 5_3 on other Dell and non-Dell systems but with different network cards and have not encountered this problem. The problem also occurs intermittently with the GENERIC kernel. This leads me to believe the cause may be related to Intel PRO/1000 and/or em driver. Any help is much appreciated? Viren -- Viren Patel Chemistry Biochemistry University of Texas at Austin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/dev/io after kernel recompiling on a 5.3 stable
after I recompiled the kernel, xorg doesn't start, stating something about cannot finding /dev/io booting with kernel.old (GENERIC) works fine what option I forgot in KERNCONF ? thanks, petre -- Login: petreName: Petre Bandac Directory: /home/petre Shell: /usr/local/bin/zsh On since Wed Feb 23 22:29 (EET) on ttyv0, idle 1:07 (messages off) No Mail. No Plan. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/io after kernel recompiling on a 5.3 stable
In the last episode (Feb 23), Petre Bandac said: after I recompiled the kernel, xorg doesn't start, stating something about cannot finding /dev/io booting with kernel.old (GENERIC) works fine what option I forgot in KERNCONF ? device io It used to be included by default, but now you have to ask for it. You may also want to add device mem. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/io after kernel recompiling on a 5.3 stable
Try searching the mailing list archive for an answer! This question has been answered before. Solution #1: Recompile your kernel with 'device io'. Solution #2: Ensure that the io.ko kernel module gets loaded at boot time. Petre Bandac schrieb: after I recompiled the kernel, xorg doesn't start, stating something about cannot finding /dev/io booting with kernel.old (GENERIC) works fine what option I forgot in KERNCONF ? thanks, petre -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/io after kernel recompiling on a 5.3 stable
what about /proc ? do I need it (if I use linux compatibility) ? In the last episode (Feb 23), Petre Bandac said: after I recompiled the kernel, xorg doesn't start, stating something about cannot finding /dev/io booting with kernel.old (GENERIC) works fine what option I forgot in KERNCONF ? device io It used to be included by default, but now you have to ask for it. You may also want to add device mem. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/io after kernel recompiling on a 5.3 stable
In the last episode (Feb 24), [EMAIL PROTECTED] said: what about /proc ? do I need it (if I use linux compatibility) ? It depends. I have /proc mounted for truss, but I don't have linprocfs mounted, and I haven't had any problems running linux apps. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3-Stable network issue
I seem to have been having a rather strange networking issue in FreeBSD 5.3-Stable (it started happening immediately after 5.2.1 and has persisted since.. I keep ³hoping² that next time I cvsup it will be fixed, but no). I downgraded back to 5.2.1-p13 and it is perfectly fine once again. *** Some background information: My FreeBSD box is my home NAT router, server, firewall, etc. It does DHCP, MX for some of my domains, secondary DNS (I got primary elsewhere), apache for some webhosting, blah blah blah. Nothing really special. It is a Dual PIII-500, 512mb ram, and a couple ATA hdd¹s. Had 3 realtek network interfaces, but down to 2 now. *** The problem: Networking simply stops or locks up. Why, I don't know. I believe initially it happened for all 3 network cards... I thought tcp/ip processing or something in the kernel got locked. It happens every 30 minutes to an hour, and lasts about 60 seconds to 120 seconds. Unfortunately, 60 seconds to 120 seconds is long enough to kill messenger (my gf does not like), online gaming, etc etc. Lately, I had taken one of the realtek cards out (it was for a several km long wireless link) and moved the server to my gf's place (where I am now 100% of the time). So now that I have the server locally and rely on it for my internet connection, this has become a real PAIN. I've noticed that I can remain ssh'd into diablo, do whatever I want while this lock issue occurs. So the lan interface rl0 is fine. The internet interface, rl1 (which goes to the cable modem) locks up. (btw, its not the cable modem as I am using my gf's now, and it did this at my place on my cable modem too, which is a different brand. Nortel at my place, motorola at my gfs). *** Attempts: I've attempted switching out network cards, and places 3 other realtek cards in. Different brands, all with different revisions (D instead of B, etc, etc). No matter what I try, nothing fixes it. The machine seems perfectly repsonsive, and I am still ssh'd in and can do whatever I want on it... But the network card going to the cable modem has stopped responding?! This never happened during 5.0-Current all throughout 5.2.1-STABLE, but anywhere beyond 5.2.1 it craps itself. *** Dmesg output: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2.1-RELEASE-p13 #2: Thu Feb 10 18:39:33 CST 2005 [EMAIL PROTECTED]:/junk/obj/junk/src/sys/DIABLO Preloaded elf kernel /boot/kernel/kernel at 0xc076c000. MPTable: OEM0 PROD Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium III/Pentium III Xeon/Celeron (504.72-MHz 686-class CPU) Origin = GenuineIntel Id = 0x673 Stepping = 3 Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,PN,MMX,FXSR,SSE real memory = 536870912 (512 MB) avail memory = 516034560 (492 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 Version 1.1 irqs 0-23 on motherboard Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00fdcf0 pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pci_cfgintr: 0:10 INTA BIOS irq 10 pci_cfgintr: 0:12 INTA BIOS irq 11 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xd3ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f at device 7.2 on pci0 pci_cfgintr: 0:7 INTD routed to irq 11 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered piix0: PIIX Timecounter port 0x5000-0x500f at device 7.3 on pci0 Timecounter PIIX frequency 3579545 Hz quality 0 pci0: display, VGA at device 8.0 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xe400-0xe4ff mem 0xd700-0xd7ff irq 10 at device 10.0 on pci0 rl0: Ethernet address: 00:00:21:f2:a5:47 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: RealTek 8139 10/100BaseTX port 0xe800-0xe8ff mem 0xd7001000-0xd70010ff irq 11 at device 12.0 on pci0 rl1: Ethernet address: 00:40:f4:90:1c:4b miibus1: MII bus on rl1 rlphy1: RealTek internal media interface on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0: Option ROMs at iomem 0xc8000-0xcbfff,0xc-0xc7fff
Problems logging w/ IPF on FreeBSD 5.3-STABLE
Hi, This question: http://lists.freebsd.org/pipermail/freebsd-questions/2004-November/066572.html appears to have no answers/responses on this list. I am experiencing the exact same problem. Since I am just learning about FreeBSD firewalls, it could be a misconfiguration error on my part. But I did the exact same thing as the other poster did. Is this a bug or did we do something wrong? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3-STABLE not saving panics ?
Hi, I Have a server that keeps panicking when under some load, and I need to understand where the problem is. I've built a kernel with makeoptions DEBUG=-g, DDB, DDB_UNATTENDED. I've added dumpdev=/dev/ad3s1b to rc.conf. But still, whenever it panicks, nothing will be logged to /var/log/messages (my 5.2.1-RELEASE workstation also logs panics there) and most important nothing will be in /var/crash/ .. I can confirm it is indeed panicking because a friend brought the server from the datacenter to his home and we are testing it. I can easily make it panic by killing init, but even these will not be dumped to /var/crash/ Have I missed something obvious ? (5.3-STABLE i386) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-STABLE not saving panics ?
On Sun, Jan 30, 2005 at 07:00:47PM +, - wrote: Hi, I Have a server that keeps panicking when under some load, and I need to understand where the problem is. I've built a kernel with makeoptions DEBUG=-g, DDB, DDB_UNATTENDED. I've added dumpdev=/dev/ad3s1b to rc.conf. But still, whenever it panicks, nothing will be logged to /var/log/messages (my 5.2.1-RELEASE workstation also logs panics there) and most important nothing will be in /var/crash/ .. I can confirm it is indeed panicking because a friend brought the server from the datacenter to his home and we are testing it. I can easily make it panic by killing init, but even these will not be dumped to /var/crash/ Have I missed something obvious ? Is savecore being run at boot time? What is displayed on the console when the system panics? Kris pgpTsTMKaGNQD.pgp Description: PGP signature
Re: 5.3-STABLE not saving panics ?
I don't see savecore being run on boot. I manually ran it and it said: savecore: No dumps found. The panics are something along panic: ain't going nowhere without my init! (I'm forcing these by sending lots of unknown signals to init) The other (real) panics are random (process-wise). I don't have much more info about these as I never get to see the server screen and they're not being logged.. Kris Kennaway wrote: On Sun, Jan 30, 2005 at 07:00:47PM +, - wrote: Hi, I Have a server that keeps panicking when under some load, and I need to understand where the problem is. I've built a kernel with makeoptions DEBUG=-g, DDB, DDB_UNATTENDED. I've added dumpdev=/dev/ad3s1b to rc.conf. But still, whenever it panicks, nothing will be logged to /var/log/messages (my 5.2.1-RELEASE workstation also logs panics there) and most important nothing will be in /var/crash/ .. I can confirm it is indeed panicking because a friend brought the server from the datacenter to his home and we are testing it. I can easily make it panic by killing init, but even these will not be dumped to /var/crash/ Have I missed something obvious ? Is savecore being run at boot time? What is displayed on the console when the system panics? Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-STABLE not saving panics ?
On Sun, Jan 30, 2005 at 10:18:40PM +, - wrote: I don't see savecore being run on boot. I manually ran it and it said: savecore: No dumps found. The panics are something along panic: ain't going nowhere without my init! (I'm forcing these by sending lots of unknown signals to init) Please try to transcribe as accurately as you can. There may be a message displayed which indicates why no dump is performed. Kris pgp3IzW00VGTL.pgp Description: PGP signature
RE: cannot boot after updating to 5.3 stable
Thanks for the answer, But i have no luck, it still won't boot : mountroot? ad0 fd0 mountrootufs:ad0s1a Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot Thanks for the answer. DL vG. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cannot boot after updating to 5.3 stable
You can boot off a live file system (the fixit CD/floppy) and examine the mountpoints which are already available on the hard disk. I have the feeling that the reason why it is not booting is, you are not setting the proper mount point. Regards, S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India -Original Message- From: Della Virgina [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 6:51 To: Subhro Cc: freebsd-questions@freebsd.org Subject: RE: cannot boot after updating to 5.3 stable Thanks for the answer, But i have no luck, it still won't boot : mountroot? ad0 fd0 mountrootufs:ad0s1a Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot Thanks for the answer. DL vG. smime.p7s Description: S/MIME cryptographic signature
Re: Problems logging w/ IPF on FreeBSD 5.3-STABLE
Nelis Lamprecht wrote: On Mon, 29 Nov 2004 18:28:06 -0800, FMorales [EMAIL PROTECTED] wrote: bash-2.05b$ cat /etc/rc.conf | grep ip ipfilter_enable=YES ipfilter_rules=/etc/ipf.rules ipmon_enable=YES ipmon_flags=-Ds change the above to read something along the lines of: ipmon_flags=-Dn /var/log/ipfilter.log remove the s in other words and put in the path to your log file to output the data. I have the same problem with my logs in 5.3, but I would like them to run through syslogd because I would like them written to another machine also. The same syslog.conf worked find on 4.10. The following /etc/syslog.conf results in firewall logs going to messages and security but not firewall.log and not remotely to kara. local0.*/var/log/firewall.log *.err;kern.debug;auth.notice;mail.crit /dev/console *.notice;authpriv.none;kern.debug;local0.none;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security auth.info;authpriv.info /var/log/auth.log mail.info /var/log/maillog lpr.info/var/log/lpd-errs ftp.info/var/log/xferlog cron.* /var/log/cron *.=debug/var/log/debug.log *.emerg * local0.*@kara If I give the command 'logger -p local0.notice where does this go ' the log goes to the local and remote machines. What am I missing? Did ipmon start forwarding to a different service? Joe. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
cannot boot after updating to 5.3 stable
Dear all, I've been updating to 5.3 stable. but after make installkernel, my box won't boot and error says : boot:boot -s ... Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot my device.hints : hint.fdc.0.at=isa hint.fdc.0.port=0x3F0 hint.fdc.0.irq=6 hint.fdc.0.drq=2 hint.fd.0.at=fdc0 hint.fd.0.drive=0 hint.fd.1.at=fdc0 hint.fd.1.drive=1 hint.ata.0.at=isa hint.ata.0.port=0x1F0 hint.ata.0.irq=14 hint.ata.1.at=isa hint.ata.1.port=0x170 hint.ata.1.irq=15 #hint.adv.0.at=isa #hint.adv.0.disabled=1 #hint.bt.0.at=isa #hint.bt.0.disabled=1 #hint.aha.0.at=isa #hint.aha.0.disabled=1 hint.aic.0.at=isa hint.aic.0.disabled=1 hint.atkbdc.0.at=isa hint.atkbdc.0.port=0x060 hint.atkbd.0.at=atkbdc hint.atkbd.0.irq=1 hint.psm.0.at=atkbdc hint.psm.0.irq=12 hint.vga.0.at=isa hint.sc.0.at=isa hint.sc.0.flags=0x100 hint.vt.0.at=isa hint.vt.0.disabled=1 hint.apm.0.disabled=1 hint.apm.0.flags=0x20 hint.pcic.0.at=isa # hint.pcic.0.irq=10 # Default to polling # hint.pcic.0.irq=10 # Default to polling hint.pcic.0.port=0x3e0 hint.pcic.0.maddr=0xd hint.pcic.1.at=isa hint.pcic.1.irq=11 hint.pcic.1.port=0x3e2 hint.pcic.1.maddr=0xd4000 hint.pcic.1.disabled=1 hint.sio.0.at=isa hint.sio.0.port=0x3F8 hint.sio.0.flags=0x10 hint.sio.0.irq=4 hint.sio.1.at=isa hint.sio.1.port=0x2F8 hint.sio.1.irq=3 hint.sio.2.at=isa hint.sio.2.disabled=1 hint.sio.2.port=0x3E8 hint.sio.2.irq=5 hint.sio.3.at=isa hint.sio.3.disabled=1 hint.sio.3.port=0x2E8 hint.sio.3.irq=9 hint.ppc.0.at=isa hint.ppc.0.irq=7 hint.ed.0.at=isa hint.ed.0.disabled=1 hint.ed.0.port=0x280 hint.ed.0.irq=10 hint.ed.0.maddr=0xd8000 hint.cs.0.at=isa hint.cs.0.disabled=1 hint.cs.0.port=0x300 hint.sn.0.at=isa hint.sn.0.disabled=1 hint.sn.0.port=0x300 hint.sn.0.irq=10 hint.ie.0.at=isa hint.ie.0.disabled=1 hint.ie.0.port=0x300 hint.ie.0.irq=10 hint.ie.0.maddr=0xd hint.fe.0.at=isa hint.fe.0.disabled=1 hint.fe.0.port=0x300 hint.lnc.0.at=isa hint.lnc.0.disabled=1 hint.lnc.0.port=0x280 hint.lnc.0.irq=10 hint.lnc.0.drq=0 my /etc/fstab : # of network filesystems before modifying this file. # # DeviceMountpoint FStype Options Dump Pass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1g /cache ufs rw 2 2 /dev/ad0s1f /home ufs rw 2 2 /dev/ad0s1e /usrufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 anyone can help me ? Dl. Vg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cannot boot after updating to 5.3 stable
Your problem is, somehow the mountpoint entries in /etc/fstab have messed up. As a result the system cant find the root file system. At the Mount Prompt type ? to get a list of all the valid mountpoints. Then manually mount all the mount points. Once you point the system the root it will straight go into the single user mode. You can then go into /dev and see what partitions are there. Mount the partitions manually and then open up /etc/fstab in your favorite text editor and make the necessary changes. The nnext boot onwards the box won't complain. BTW, you wont be able to open any text editor until and unless /usr is mounted. Because all the binaries (including the text editor, vi in my case) resides in /usr. Regards, S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Rino M Nur Sent: Saturday, January 29, 2005 8:03 To: freebsd-questions@freebsd.org Subject: cannot boot after updating to 5.3 stable Dear all, I've been updating to 5.3 stable. but after make installkernel, my box won't boot and error says : boot:boot -s ... Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot my device.hints : hint.fdc.0.at=isa hint.fdc.0.port=0x3F0 hint.fdc.0.irq=6 hint.fdc.0.drq=2 hint.fd.0.at=fdc0 hint.fd.0.drive=0 hint.fd.1.at=fdc0 hint.fd.1.drive=1 hint.ata.0.at=isa hint.ata.0.port=0x1F0 hint.ata.0.irq=14 hint.ata.1.at=isa hint.ata.1.port=0x170 hint.ata.1.irq=15 #hint.adv.0.at=isa #hint.adv.0.disabled=1 #hint.bt.0.at=isa #hint.bt.0.disabled=1 #hint.aha.0.at=isa #hint.aha.0.disabled=1 hint.aic.0.at=isa hint.aic.0.disabled=1 hint.atkbdc.0.at=isa hint.atkbdc.0.port=0x060 hint.atkbd.0.at=atkbdc hint.atkbd.0.irq=1 hint.psm.0.at=atkbdc hint.psm.0.irq=12 hint.vga.0.at=isa hint.sc.0.at=isa hint.sc.0.flags=0x100 hint.vt.0.at=isa hint.vt.0.disabled=1 hint.apm.0.disabled=1 hint.apm.0.flags=0x20 hint.pcic.0.at=isa # hint.pcic.0.irq=10 # Default to polling # hint.pcic.0.irq=10 # Default to polling hint.pcic.0.port=0x3e0 hint.pcic.0.maddr=0xd hint.pcic.1.at=isa hint.pcic.1.irq=11 hint.pcic.1.port=0x3e2 hint.pcic.1.maddr=0xd4000 hint.pcic.1.disabled=1 hint.sio.0.at=isa hint.sio.0.port=0x3F8 hint.sio.0.flags=0x10 hint.sio.0.irq=4 hint.sio.1.at=isa hint.sio.1.port=0x2F8 hint.sio.1.irq=3 hint.sio.2.at=isa hint.sio.2.disabled=1 hint.sio.2.port=0x3E8 hint.sio.2.irq=5 hint.sio.3.at=isa hint.sio.3.disabled=1 hint.sio.3.port=0x2E8 hint.sio.3.irq=9 hint.ppc.0.at=isa hint.ppc.0.irq=7 hint.ed.0.at=isa hint.ed.0.disabled=1 hint.ed.0.port=0x280 hint.ed.0.irq=10 hint.ed.0.maddr=0xd8000 hint.cs.0.at=isa hint.cs.0.disabled=1 hint.cs.0.port=0x300 hint.sn.0.at=isa hint.sn.0.disabled=1 hint.sn.0.port=0x300 hint.sn.0.irq=10 hint.ie.0.at=isa hint.ie.0.disabled=1 hint.ie.0.port=0x300 hint.ie.0.irq=10 hint.ie.0.maddr=0xd hint.fe.0.at=isa hint.fe.0.disabled=1 hint.fe.0.port=0x300 hint.lnc.0.at=isa hint.lnc.0.disabled=1 hint.lnc.0.port=0x280 hint.lnc.0.irq=10 hint.lnc.0.drq=0 my /etc/fstab : # of network filesystems before modifying this file. # # DeviceMountpoint FStype Options Dump Pass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1g /cache ufs rw 2 2 /dev/ad0s1f /home ufs rw 2 2 /dev/ad0s1e /usrufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 anyone can help me ? Dl. Vg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature
RE: cannot boot after updating to 5.3 stable
On Fri, 2005-01-28 at 22:35, Subhro wrote: Your problem is, somehow the mountpoint entries in /etc/fstab have messed up. As a result the system cant find the root file system. At the Mount Prompt type ? to get a list of all the valid mountpoints. Then manually mount all the mount points. Once you point the system the root it will straight go into the single user mode. You can then go into /dev and see what partitions are there. Mount the partitions manually and then open up /etc/fstab in your favorite text editor and make the necessary changes. The nnext boot onwards the box won't complain. BTW, you wont be able to open any text editor until and unless /usr is mounted. Because all the binaries (including the text editor, vi in my case) resides in /usr. There is a primitive but usable editor called ed in /bin. It dates back to the stone age of computing, and you will do better if you can practise with it (or at least print out the manual on paper) before you really need it. It is there for emergencies like fixing up /etc/fstab. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cannot boot after updating to 5.3 stable
Thanks Mike :-) Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India -Original Message- From: Mike Jeays [mailto:[EMAIL PROTECTED] Sent: Saturday, January 29, 2005 9:28 To: Subhro Cc: 'Rino M Nur'; freebsd-questions@freebsd.org Subject: RE: cannot boot after updating to 5.3 stable On Fri, 2005-01-28 at 22:35, Subhro wrote: Your problem is, somehow the mountpoint entries in /etc/fstab have messed up. As a result the system cant find the root file system. At the Mount Prompt type ? to get a list of all the valid mountpoints. Then manually mount all the mount points. Once you point the system the root it will straight go into the single user mode. You can then go into /dev and see what partitions are there. Mount the partitions manually and then open up /etc/fstab in your favorite text editor and make the necessary changes. The nnext boot onwards the box won't complain. BTW, you wont be able to open any text editor until and unless /usr is mounted. Because all the binaries (including the text editor, vi in my case) resides in /usr. There is a primitive but usable editor called ed in /bin. It dates back to the stone age of computing, and you will do better if you can practise with it (or at least print out the manual on paper) before you really need it. It is there for emergencies like fixing up /etc/fstab. smime.p7s Description: S/MIME cryptographic signature
Problem to stabilize from 4.11 to 5.3 stable
Dear all, I've configured some error in stabilized to 5.3 stable from 4.11 stable. When i try to stabilize from 4.9RC to 4.11stable there's no problem at all. But when i try to cvsup to 5.3stable i found some error like this : -- cc -O3 -pipe -funroll-loops -ffast-math -O3 -march=pentiumpro -I/cache/src/lib/libc/include -I/cache/src/lib/libc/../../include -I/cache/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE -I/cache/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/cache/src/lib/libc -DPOSIX_MISTAKE -I/cache/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/cache/src/lib/libc/rpc -DYP -DHESIOD -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /cache/src/lib/libc/net/res_data.c cc -O3 -pipe -funroll-loops -ffast-math -O3 -march=pentiumpro -I/cache/src/lib/libc/include -I/cache/src/lib/libc/../../include -I/cache/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE -I/cache/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/cache/src/lib/libc -DPOSIX_MISTAKE -I/cache/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/cache/src/lib/libc/rpc -DYP -DHESIOD -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /cache/src/lib/libc/net/res_debug.c In file included from /cache/src/lib/libc/net/res_debug.c:786: /cache/src/lib/libc/net/res_debug.c: In function `__loc_aton': /cache/src/lib/libc/net/res_debug.c:576: warning: passing arg 1 of `precsize_aton' from incompatible pointer type In file included from /cache/src/lib/libc/net/res_debug.c:797: /cache/src/lib/libc/net/res_debug.c:576: warning: passing arg 1 of `precsize_aton' from incompatible pointer type In file included from /cache/src/lib/libc/net/res_debug.c:808: /cache/src/lib/libc/net/res_debug.c:576: warning: passing arg 1 of `precsize_aton' from incompatible pointer type *** Error code 1 Stop in /cache/src/lib/libc. *** Error code 1 Stop in /cache/src/lib. *** Error code 1 Stop in /cache/src. *** Error code 1 Stop in /cache/src. *** Error code 1 Stop in /cache/src. *** Error code 1 Stop in /cache/src. -- First i try to change cvsup server to another, but no luck. Can anyone help me. Many Thanks. DVg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem to stabilize from 4.11 to 5.3 stable
On Wed, Jan 26, 2005 at 11:56:42AM +0700, Della Virgina wrote: Dear all, I've configured some error in stabilized to 5.3 stable from 4.11 stable. When i try to stabilize from 4.9RC to 4.11stable there's no problem at all. But when i try to cvsup to 5.3stable i found some error like this : -- cc -O3 -pipe -funroll-loops -ffast-math -O3 -march=pentiumpro Hold it right there, cowboy! What does the make.conf manpage say about using extreme optimization levels like -O3? Kris pgpGeSIwwxKhU.pgp Description: PGP signature
missing /dev/bktr etc on FreeBSD-5.3-STABLE
Hi, I'm trying to make my TV-card work on my box, using FBSD-5.3-STABLE. For this I put the following lines in my Kernel config. file: device bktr device iicbus device iicbb device smbus compiled the new kernel, installed it and rebooted. But dmesg shows nothing corresponding to these lines nor are the devices present in /dev/ Can anybody give me an idea how to get to problem solved ?? Responses are very apreciated. Regards, Carlo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: missing /dev/bktr etc on FreeBSD-5.3-STABLE
On Tuesday 25 January 2005 02:34, [EMAIL PROTECTED] wrote: Hi, I'm trying to make my TV-card work on my box, using FBSD-5.3-STABLE. For this I put the following lines in my Kernel config. file: devicebktr deviceiicbus deviceiicbb devicesmbus compiled the new kernel, installed it and rebooted. But dmesg shows nothing corresponding to these lines nor are the devices present in /dev/ Can anybody give me an idea how to get to problem solved ?? Responses are very apreciated. I have this in my /etc/devfs.conf: permcd0 0660 permcd1 0660 permda0s1 0660 permda1s1 0660 permxpt00660 permxpt10660 permpass0 0660 permpass1 0660 permpass2 0660 permpass3 0660 permlpt00660 permbktr0 0660 permtuner0 0660 permcuaa0 0660 Everyting up to lpt is for using atacam functionality (e.g. CD burning). Bktr and tuner are for the capture card (I have an old Miro Bt848). And the /boot/loader.conf has: sound_load=YES snd_emu10k1_load=YES nvidia_load=YES bktr_load=YES linux_load=YES So here I load the bktr module upon booting. I don't use any special kernel config for bktr (I have other options for other hardware). As far as detecting your card, try pciconf -l or -lv. Also dmesg can show you what it has detected and done so far. My card because it's so old needs some PnP probing but even that works. Kldstat shows which modules are loaded. HTH Dan Regards, Carlo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: copying from DVD drive causes crash: vm_fault: pager readerror, pid 13421 (cp) on FreeBSD 5.3-STABLE
Hello I observe a similiar behaviour here on an ASUS Laptop with a MATSHITAUJ-831D/1.00 DVD-RW Drive. Altough only with DVD's, but not with CD's. Installed is FreeBSD 5.3-RELEASE-p2. The only difference to the GENERIC kernel is that I added the device atapicam to the kernel. The failure occures with both way accessing the drive (acd0 and cd0). If you need more output, pls. tell me. Chris On Thu, 6 Jan 2005, O. Hartmann wrote: Daniel O'Connor schrieb: On Thu, 6 Jan 2005 23:16, O. Hartmann wrote: Doing dd from the DVD drive (NEC ND 3500AG/2.18) fails in a corrupt image afterwards, copying with 'cp' from a inserted CD triggers the shown error and box dies immediately: Jan 6 12:17:20 edda kernel: cd9660: RockRidge Extension Jan 6 12:17:50 edda kernel: acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4ABORTED Jan 6 12:18:07 edda last message repeated 3 times Jan 6 12:29:44 edda kernel: cd9660: RockRidge Extension Jan 6 12:30:54 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:30:54 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:30:58 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:30:58 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:01 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:31:01 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:08 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:31:08 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:19 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4A Same happens when trying to to a 'tar ztf file.foo' (tar archive located on DVD) - FreeBSD dies and freezes immediately. Does it panic or hang? The DVD has errors on it which is why you can't read it.. Obviously the OS crashing when presented with bad media is not a good thing :) The box hang. The media is all right, I tried it on a FreeBSD 4.10 box and a Windows box (equipted with the same DVD-RW drive, running on a different hardware platform). Writing 'clear' images to the drive results in corrupted media, either DVD and/or CD-R/W. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
copying from DVD drive causes crash: vm_fault: pager read error, pid 13421 (cp) on FreeBSD 5.3-STABLE
Doing dd from the DVD drive (NEC ND 3500AG/2.18) fails in a corrupt image afterwards, copying with 'cp' from a inserted CD triggers the shown error and box dies immediately: Jan 6 12:17:20 edda kernel: cd9660: RockRidge Extension Jan 6 12:17:50 edda kernel: acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4ABORTED Jan 6 12:18:07 edda last message repeated 3 times Jan 6 12:29:44 edda kernel: cd9660: RockRidge Extension Jan 6 12:30:54 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:30:54 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:30:58 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:30:58 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:01 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:31:01 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:08 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:31:08 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:19 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4A Same happens when trying to to a 'tar ztf file.foo' (tar archive located on DVD) - FreeBSD dies and freezes immediately. Box is a FreeBSD 5.3-STABLE box (cvsupdated and builtworld today). Hardware is a ASUS CUR-DLS based mainboard, SMP disabled, dmesg shown here: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #23: Thu Jan 6 09:45:18 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/EDDA ACPI APIC Table: ASUS CUR-DLS Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (1000.04-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE real memory = 1073721344 (1023 MB) avail memory = 1041166336 (992 MB) ioapic0 Version 1.1 irqs 0-15 on motherboard ioapic1 Version 1.1 irqs 16-31 on motherboard netsmb_dev: loaded npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS CUR-DLS on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: display, VGA at device 7.0 (no driver attached) isab0: PCI-ISA bridge port 0xe800-0xe80f at device 15.0 on pci0 isa0: ISA bus on isab0 atapci0: ServerWorks ROSB4 UDMA33 controller port 0xd400-0xd40f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ohci0: OHCI (generic) USB controller mem 0xfc00-0xfc000fff irq 9 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ugen0: OmniVision OV511+ Camera, rev 1.00/1.00, addr 2 pcib1: ACPI Host-PCI bridge on acpi0 pci1: ACPI PCI bus on pcib1 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xd000-0xd03f mem 0xfb80-0xfb81 irq 2 1 at device 2.0 on pci1 em0: Ethernet address: 00:07:e9:14:8f:7b em0: Speed:N/A Duplex:N/A sym0: 1010-33 port 0xb800-0xb8ff mem 0xfa80-0xfa801fff,0xfb00-0xfb0003ff irq 24 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: [GIANT-LOCKED] sym1: 1010-33 port 0xb400-0xb4ff mem 0xf980-0xf9801fff,0xfa00-0xfa0003ff irq 25 at device 5.1 on pci1 sym1: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. sym1: [GIANT-LOCKED] atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: ECP parallel printer port port 0x778-0x77a,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port fdc0: floppy drive
Re: copying from DVD drive causes crash: vm_fault: pager read error, pid 13421 (cp) on FreeBSD 5.3-STABLE
On Thu, 6 Jan 2005 23:16, O. Hartmann wrote: Doing dd from the DVD drive (NEC ND 3500AG/2.18) fails in a corrupt image afterwards, copying with 'cp' from a inserted CD triggers the shown error and box dies immediately: Jan 6 12:17:20 edda kernel: cd9660: RockRidge Extension Jan 6 12:17:50 edda kernel: acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4ABORTED Jan 6 12:18:07 edda last message repeated 3 times Jan 6 12:29:44 edda kernel: cd9660: RockRidge Extension Jan 6 12:30:54 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:30:54 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:30:58 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:30:58 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:01 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:31:01 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:08 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:31:08 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:19 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4A Same happens when trying to to a 'tar ztf file.foo' (tar archive located on DVD) - FreeBSD dies and freezes immediately. Does it panic or hang? The DVD has errors on it which is why you can't read it.. Obviously the OS crashing when presented with bad media is not a good thing :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpzrfmq7GHO6.pgp Description: PGP signature
Re: copying from DVD drive causes crash: vm_fault: pager readerror, pid 13421 (cp) on FreeBSD 5.3-STABLE
Daniel O'Connor schrieb: On Thu, 6 Jan 2005 23:16, O. Hartmann wrote: Doing dd from the DVD drive (NEC ND 3500AG/2.18) fails in a corrupt image afterwards, copying with 'cp' from a inserted CD triggers the shown error and box dies immediately: Jan 6 12:17:20 edda kernel: cd9660: RockRidge Extension Jan 6 12:17:50 edda kernel: acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4ABORTED Jan 6 12:18:07 edda last message repeated 3 times Jan 6 12:29:44 edda kernel: cd9660: RockRidge Extension Jan 6 12:30:54 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:30:54 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:30:58 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:30:58 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:01 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:31:01 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:08 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4ABORTED Jan 6 12:31:08 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:19 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4A Same happens when trying to to a 'tar ztf file.foo' (tar archive located on DVD) - FreeBSD dies and freezes immediately. Does it panic or hang? The DVD has errors on it which is why you can't read it.. Obviously the OS crashing when presented with bad media is not a good thing :) The box hang. The media is all right, I tried it on a FreeBSD 4.10 box and a Windows box (equipted with the same DVD-RW drive, running on a different hardware platform). Writing 'clear' images to the drive results in corrupted media, either DVD and/or CD-R/W. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade to 5.3-STABLE broke X?
On Wed, 29 Dec 2004, Adam Fabian wrote: I upgraded from 6.7.0 to 6.8.1 and also got obscure (but different) error messages. The 5.3 packages on FreeBSD's FTP servers are 6.7.0. After looking a bit and not really finding a solution to my problem, I just downloaded the binary packages and downgraded back to 6.7.0. (This is probably a lot easier than compiling, since you'd probably have to use portdowngrade on a lot of ports, or do it manually, or some such.) Apparently this is a known issue with 6.8.1 and the i810 driver; see Problem Report ports/75425 for more info (and to contribute further info). http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/75425 -- Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3-STABLE crashes on Dell PowerEdge 2850
On Tue, 28 Dec 2004 19:50:07 -0600, you wrote: I think this could be a ACPI problem I had similar errors with P4 HTT cpu on intel 865 desktop board but was working perfectly on asus 875.. Did you try without ACPI ?? The kernel conf tells me following: #Compile acpi in statically since the module isn't built properly.Most # machines which support large amounts of memory require acpi. device acpi So it's compiled with this setting. The server has 6 GB of memory. I have tried to disable logical processor and boot with the loader option without ACPI, but the server is still crashing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade to 5.3-STABLE broke X?
Dave Horsfall [EMAIL PROTECTED] writes: Was running 5.3-RELEASE (from CD) on R31 Thinkpad, when I decided to take advantage of the excellent upgrade guide posted here recently by Richard Bejtlich, and give -STABLE a spin, followed by a portupgrade. Now, it's unclear at what point the breakage happened, because one followed the other straight away (I know, a big mistake). Anyway, after what seemed like an eternity (and probably maxing out my ADSL link in the process) everything finished, and I fired up X (X.org, which I had originally, so no issues with XFree86 etc as mentioned in UPDATING). Obscure error messages: (EE) I810(0): Failed to allocate HW (ARGB) cursor space. (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. Fatal server error: Caught signal 11. Server aborting This used to work, so what broke? I can't even run xorgcfg either, for the same reason! I note that Xorg went from 6.7.0 to 6.8.1, and I poked around wiki.x.org hoping to get release notes etc, to no avail - the links are broken. It also offered the advice of running xorgcfg (see above), or sending mail to [EMAIL PROTECTED] (which turned out to be a mailing list to which one has to subscribe). Under the Known issues after updating page, it says to be found and written down... (I kid you not). What do I do now? Reinstall FreeBSD? Install XFree86 instead? Somehow downgrade to 6.7.0 until wiki.x.org gets its act together? Do I need some hitherto-unneeded kernel options? It kind of depends on your X configuration, I would think. Were you using DRI or not? If so, did you rebuild it? Were you using third-party drivers (e.g., NVidia)? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade to 5.3-STABLE broke X?
On Thu, 29 Dec 2004, Lowell Gilbert wrote: It kind of depends on your X configuration, I would think. Were you using DRI or not? If so, did you rebuild it? Were you using third-party drivers (e.g., NVidia)? DRI is not supported (the reason for one of the errors) because hardware cursors aren't supported (the reason for the other error). Disabling both still gives me a SIGSEGV, with a useless coredump (stack frames corrupted). And I was using whatever native drivers were present. I got a private reply saying there are issues with this version and my hardware, so I'll take it to the freebsd-x11 list as he suggested. -- Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade to 5.3-STABLE broke X?
On Tue, Dec 28, 2004 at 12:57:24PM +1100, Dave Horsfall wrote: Obscure error messages: I note that Xorg went from 6.7.0 to 6.8.1, and I poked around I upgraded from 6.7.0 to 6.8.1 and also got obscure (but different) error messages. The 5.3 packages on FreeBSD's FTP servers are 6.7.0. After looking a bit and not really finding a solution to my problem, I just downloaded the binary packages and downgraded back to 6.7.0. (This is probably a lot easier than compiling, since you'd probably have to use portdowngrade on a lot of ports, or do it manually, or some such.) What do I do now? Reinstall FreeBSD? Install XFree86 instead? Somehow downgrade to 6.7.0 until wiki.x.org gets its act together? Newer isn't always better... and it *is* X. It's been the same X11R6 for years. ;) -- Adam Fabian ([EMAIL PROTECTED]) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3-STABLE crashes on Dell PowerEdge 2850
I have installed FreeBSD 5.3-STABLE i386 on a new Dell PowerEdge 2850, but it crashes under load. I can't figure why. Has anyone succeeded running FreeBSD 5.3 on this hardware? Following is the output from console made by two random crashes. Crash #1: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc039733e stack pointer = 0x10:0xee15dc44 frame pointer = 0x10:0xee15dc6c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 122 (pagedaemon) trap number = 12 panic: page fault cpuid = 0 boot() called on cpu#0 Uptime: 4m58s Cannot dump. No dump device definded. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#0 cpu_reset: Stopping other CPUs spin lock sched lock held by 0xc8b97190 for 5 seconds Crash #2: fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:xc3555da stack pointer = 0x10:0xf08adaa4 frame pointer = 0x10:0xf08adacc code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 610 (sshd) trap number = 12 panic: page fault cpuid = 1 Fatal double fault: eip = 0xc032674a esp = 0xec564ff8 ebp = 0xec565010 cpuid = 2; apic id = 06 Fatal double fault: eip = 0xc032674a esp = 0xee46eff4 ebp = 0xee46f00c cpuid = 3; apic id = 07 spin lock sched lock held by 0xc8ad97d0 for 5 seconds Running for example make buildworld or rsync could make the server crash, but it doesn't seems to crash, when it runs the distributed.net client (100% CPU load), so I don't think it is a overheating problem. The server has following configuration: 2x Intel Xeon 3.4 GHz (800 MHz FSB), 6x 1 GB DDR2 ECC RAM and Perc 4e/Di (LSI Logic/amr driver). I have compiled the kernel with SMP of course and PAE because of 4 GB memory. I have removed all the unnecessary devices. I have been running memtest (http://www.memtest.org/) without any errors. Would it maybe be better to run the AMD64 version of FreeBSD 5.3? I think the i386 version should be more stable? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 5.3-STABLE crashes on Dell PowerEdge 2850
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian R. Sent: Tuesday, December 28, 2004 5:47 PM To: freebsd-questions@freebsd.org Subject: FreeBSD 5.3-STABLE crashes on Dell PowerEdge 2850 I have installed FreeBSD 5.3-STABLE i386 on a new Dell PowerEdge 2850, but it crashes under load. I can't figure why. Has anyone succeeded running FreeBSD 5.3 on this hardware? Following is the output from console made by two random crashes. Crash #1: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc039733e stack pointer = 0x10:0xee15dc44 frame pointer = 0x10:0xee15dc6c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 122 (pagedaemon) trap number = 12 panic: page fault cpuid = 0 boot() called on cpu#0 Uptime: 4m58s Cannot dump. No dump device definded. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#0 cpu_reset: Stopping other CPUs spin lock sched lock held by 0xc8b97190 for 5 seconds Crash #2: fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:xc3555da stack pointer = 0x10:0xf08adaa4 frame pointer = 0x10:0xf08adacc code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 610 (sshd) trap number = 12 panic: page fault cpuid = 1 Fatal double fault: eip = 0xc032674a esp = 0xec564ff8 ebp = 0xec565010 cpuid = 2; apic id = 06 Fatal double fault: eip = 0xc032674a esp = 0xee46eff4 ebp = 0xee46f00c cpuid = 3; apic id = 07 spin lock sched lock held by 0xc8ad97d0 for 5 seconds Running for example make buildworld or rsync could make the server crash, but it doesn't seems to crash, when it runs the distributed.net client (100% CPU load), so I don't think it is a overheating problem. The server has following configuration: 2x Intel Xeon 3.4 GHz (800 MHz FSB), 6x 1 GB DDR2 ECC RAM and Perc 4e/Di (LSI Logic/amr driver). I have compiled the kernel with SMP of course and PAE because of 4 GB memory. I have removed all the unnecessary devices. I have been running memtest (http://www.memtest.org/) without any errors. Would it maybe be better to run the AMD64 version of FreeBSD 5.3? I think the i386 version should be more stable? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I think this could be a ACPI problem I had similar errors with P4 HTT cpu on intel 865 desktop board but was working perfectly on asus 875.. Did you try without ACPI ?? Best regards, Andras Kende http://www.kende.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrade to 5.3-STABLE broke X?
Was running 5.3-RELEASE (from CD) on R31 Thinkpad, when I decided to take advantage of the excellent upgrade guide posted here recently by Richard Bejtlich, and give -STABLE a spin, followed by a portupgrade. Now, it's unclear at what point the breakage happened, because one followed the other straight away (I know, a big mistake). Anyway, after what seemed like an eternity (and probably maxing out my ADSL link in the process) everything finished, and I fired up X (X.org, which I had originally, so no issues with XFree86 etc as mentioned in UPDATING). Obscure error messages: (EE) I810(0): Failed to allocate HW (ARGB) cursor space. (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. Fatal server error: Caught signal 11. Server aborting This used to work, so what broke? I can't even run xorgcfg either, for the same reason! I note that Xorg went from 6.7.0 to 6.8.1, and I poked around wiki.x.org hoping to get release notes etc, to no avail - the links are broken. It also offered the advice of running xorgcfg (see above), or sending mail to [EMAIL PROTECTED] (which turned out to be a mailing list to which one has to subscribe). Under the Known issues after updating page, it says to be found and written down... (I kid you not). What do I do now? Reinstall FreeBSD? Install XFree86 instead? Somehow downgrade to 6.7.0 until wiki.x.org gets its act together? Do I need some hitherto-unneeded kernel options? -- Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Wheel Mouse in 5.3 STABLE
I have successfully loaded 5.3 and cvsuped to STABLE. Since loading Xorg, I have been trying to use my wheel on my mouse. I have edited the xorg conf file that I created and followed the hand book and even some threads from this list. Can someone please point me in the right direction for this? I'm going nuts! (Short trip by the way) Thanks in advance, Ron Clark __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
On Thu, Dec 16, 2004 at 05:58:08AM -0800, Ronnie Clark wrote: I have successfully loaded 5.3 and cvsuped to STABLE. Since loading Xorg, I have been trying to use my wheel on my mouse. I have edited the xorg conf file that I created and followed the hand book and even some threads from this list. i use my wheel mouse with this conf in xorg.conf Section InputDevice Identifier Mouse2 Driver mouse Option Protocol Auto Option Device/dev/sysmouse Option ZAxisMapping 4 5 EndSection Can someone please point me in the right direction for this? I'm going nuts! (Short trip by the way) Thanks in advance, Ron Clark __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ---end quoted text--- -- Pablo Allietti LACNIC -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
Ronnie Clark wrote: I have successfully loaded 5.3 and cvsuped to STABLE. Since loading Xorg, I have been trying to use my wheel on my mouse. I have edited the xorg conf file that I created and followed the hand book and even some threads from this list. Can someone please point me in the right direction for this? I'm going nuts! (Short trip by the way) since you don't give much information about the problem, e.g. what errors you're seeing, it's hard to say for sure what's wrong... but i'll try anyways. i have this in my config file Section InputDevice Identifier Mouse0 Driver mouse Option Protocol Auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 EndSection the mouse is detected as ums0: Microsoft Basic Optical Mouse, rev 1.10/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. and don't forget a line like usbd_enable=YES in /etc/rc.conf -- and it works. hth, phil. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
All, Thanks for the responses. I hope this will help: Currently I have this in my xorg.conf.new file: Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 EndSection I start Xorg by using the startx method, and it starts KDE just fine. When I try to start xorg by typing Xorg, KDE does not start. Back to the conf file, I have tried to define Options Buttons 5 (did not work) Options ZAxisMapping Y (from a previous thread, also did not work) So, does it matter where my xorg.conf.new file is at? Mine is in the /root directory, which is where it was originally configured. Is there another conf file I need to edit? again, I'm stuck on this one. If this is not enough about the problem, please feel free to ask me questions, as I would love to solve this today. Thanks again, Ron Clark --- Phil Schulz [EMAIL PROTECTED] wrote: Ronnie Clark wrote: I have successfully loaded 5.3 and cvsuped to STABLE. Since loading Xorg, I have been trying to use my wheel on my mouse. I have edited the xorg conf file that I created and followed the hand book and even some threads from this list. Can someone please point me in the right direction for this? I'm going nuts! (Short trip by the way) since you don't give much information about the problem, e.g. what errors you're seeing, it's hard to say for sure what's wrong... but i'll try anyways. i have this in my config file Section InputDevice Identifier Mouse0 Driver mouse Option Protocol Auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 EndSection the mouse is detected as ums0: Microsoft Basic Optical Mouse, rev 1.10/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. and don't forget a line like usbd_enable=YES in /etc/rc.conf -- and it works. hth, phil. __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
Ronnie Clark extolled: So, does it matter where my xorg.conf.new file is at? Mine is in the /root directory, which is where it was originally configured. Is there another conf file I need to edit? again, I'm stuck on this one. If this is not enough about the problem, please feel free to ask me questions, as I would love to solve this today. Thanks again, Ron Clark Standard location is /etc/X11/xorg.conf Or, following the instructions printed by Xorg -config, run Xorg -config /path/to/xorg.conf.new -- ___ Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
Ronnie Clark wrote: (**) Option Protocol auto (**) Mouse0: Device: /dev/sysmouse (**) Mouse0: Protocol: auto (**) Option CorePointer (**) Mouse0: Core Pointer (**) Option Device /dev/sysmouse (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 5 (II) Keyboard Keyboard0 handled by legacy driver (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) (II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Mouse0: SetupAuto: protocol is SysMouse According to this, it *should* work, right? Still stumped, and not working... does your mouse work on the console, i.e. do you see a cursor moveing when your on the console and move your mouse? regards, phil. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
Ronnie Clark extolled: OK, I have generated a new xorg.conf.new file. I have edited it and copied it over to /etc/X11. Here is a snip of the xorg log file: Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. ... (**) Option Protocol auto (**) Mouse0: Device: /dev/sysmouse (**) Mouse0: Protocol: auto (**) Option CorePointer (**) Mouse0: Core Pointer (**) Option Device /dev/sysmouse (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 5 (II) Keyboard Keyboard0 handled by legacy driver (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) (II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Mouse0: SetupAuto: protocol is SysMouse According to this, it *should* work, right? Still stumped, and not working... Thanks again. Ron Clark aside You really should not top post, although it seems to be a hard abit to get away from./aside Just to make sure, you copied it as xorg.conf, not xorg.conf.new, right? -- ___ Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
Yes to both you and Phil. Thanks, Ron Clark __ Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
On Thu, 2004-12-16 at 09:42 -0800, Ronnie Clark wrote: Yes to both you and Phil. Thanks, Ron Clark If it is a usb mouse, make sure the usbd is translating the wheel events. There is some stuff in the handbook on this. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
I managed to get my wheel working in xorg, but this required disabling it for the console. This is a sub-optimal solution, but it works for me because I don't often want to use the mouse in the console---sometimes I would like to but I didn't want to fight with it anymore. Here is what I did: comment out moused stuff in /etc/rc.conf: #moused_enable=YES #moused_port=/dev/psm0 #moused_type=intellimouse and in /etc/X11/xorg.conf: Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/psm0 Option ZAxisMapping 4 5 I think you are trying to get a USB mouse working (am I remembering that correctly?) In any case I am using a ps/2 mouse, I don't know if that makes a difference for the Option Device /dev/psm0 line. As I mentioned before this will make the mouse non-functional in the console (still works in xterm thought). Conan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
Well after my last post I started playing with things again, and have the mouse working in the console and the wheel working in xorg. /etc/rc.conf moused_enable=YES #moused_port=/dev/psm0 #moused_type=intellimouse /etc/X11/xorg.conf: Identifier Mouse1 Driver mouse Option ProtocolAuto Option Device /dev/sysmouse # Option Device /dev/psm0 Option ZAxisMapping 4 5 I just did some more checking apperently it is the moused_type=intellimouse line that was causing me problems, because the following also works: /etc/rc.conf moused_enable=YES moused_port=/dev/psm0 #moused_type=intellimouse I hope you get yours working. TTYL Conan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wheel Mouse in 5.3 STABLE
OK, I have generated a new xorg.conf.new file. I have edited it and copied it over to /etc/X11. Here is a snip of the xorg log file: Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. ... (**) Option Protocol auto (**) Mouse0: Device: /dev/sysmouse (**) Mouse0: Protocol: auto (**) Option CorePointer (**) Mouse0: Core Pointer (**) Option Device /dev/sysmouse (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 5 (II) Keyboard Keyboard0 handled by legacy driver (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) (II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Mouse0: SetupAuto: protocol is SysMouse According to this, it *should* work, right? Still stumped, and not working... Thanks again. Ron Clark --- Dan Kilbourne [EMAIL PROTECTED] wrote: Ronnie Clark extolled: So, does it matter where my xorg.conf.new file is at? Mine is in the /root directory, which is where it was originally configured. Is there another conf file I need to edit? again, I'm stuck on this one. If this is not enough about the problem, please feel free to ask me questions, as I would love to solve this today. Thanks again, Ron Clark Standard location is /etc/X11/xorg.conf Or, following the instructions printed by Xorg -config, run Xorg -config /path/to/xorg.conf.new -- ___ Dan __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3-STABLE: PHP 5.0.2 won't compile
Hello. Under FreeBSD 5.3-STABLE, PHP 5.0.2 from ports collection will not compile anymore. Compilation ends up with ext/standard/dns.lo(.text+0x1d49): In function `.L166': : undefined reference to `res_ninit' ext/standard/dns.lo(.text+0x1db5): In function `.L166': : undefined reference to `res_nmkquery' ext/standard/dns.lo(.text+0x1de7): In function `.L166': : undefined reference to `res_nsend' ext/standard/dns.lo(.text+0x1f6a): In function `.L166': : undefined reference to `res_nclose' *** Error code 1 I found some threads about BIND/BIND9 relating things and it seemed to me that BIND9 is neccessary to compile PHP 5.0.2 properly but I thought BIND9 is now standard in 5.3. In /etc/make.conf with WITH_BIND_LIBS= true enabled, I built world again hoping I get a possibly missing library or .h file to get php compiling as expected, but with no success. Is there a hint to come along with this? Thanks a lot Oliver ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
twa error message on 5.3 STABLE amd
Any idea what to do about this? twa0: Unable to sync time with ctlr! We get one of these occasionally. FreeBSD FreeBSD 5.3-STABLE #3: (AMD64) CPU: AMD Opteron(tm) Processor 250 (2405.47-MHz K8-class CPU) twa0: 3ware 9000 series Storage Controller port 0x3000-0x30ff mem 0xfd80-0xfdff,0xfd02-0xfd0200ff irq 26 at device 2.0 on pci2 twa0: [GIANT-LOCKED] twa0: 4 ports, Firmware FE9X 2.04.00.003, BIOS BE9X 2.03.01.047 da0 at twa0 bus 0 target 0 lun 0 da0: 3ware Logical Disk 00 1.00 Fixed Direct Access SCSI-0 device da0: 100.000MB/s transfers da0: 238408MB (488259584 512 byte sectors: 255H 63S/T 30392C) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: HTT/SMP servers instability on 5.3-STABLE]
On Friday 10 December 2004 19:57, Colin J. Raven wrote: On Dec 10, Toomas Aas launched this into the bitstream: Colin J. Raven wrote: On Dec 10, Toomas Aas launched this into the bitstream: For more than a month now, I've been running a Dual Xeon 2000 system (IBM eServer xSeries 225) with 5.3-RC2 and later upgraded to 5.3-RELEASE and I have no problems at all. Hyperthreading is disabled in BIOS, ACPI is enabled. Excuse me for jumping into this thread but could you elaborate as to why you have Nyperthreading disabled? I'm afraid I can't give you any good technical reasons. I simply think of HTT as Intel marketing blurb, meant to make you feel like you are getting two CPUs for the price of one. Well, actually it's still only one CPU. I've been running another single Xeon 2.4 box for more than a year. Initially, I ran several months with HTT enabled. Then I ran several months with HTT disabled. I didn't really notice any performance difference. Well thanks for sharing those observations. Until I read what you said I *assumed* that there was a performance difference with HTT enabled. The specs seem to show that there *is* a theoretical difference, yet clearly according to your observations there just isn't any difference of earth shaking proportions. Isn't the point of HTT that a CPU holds several threads from the *same* process. So if your software isn't multithreaded, there's no benifit. UNIX software tends to fork single-threaded process, rather than create new threads, so it benefits from SMP, but not HTT. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: HTT/SMP servers instability on 5.3-STABLE]
Hi, I have a Dual Xeon 2.4 and a Dual Xeon 2.8 servers running with HyperThreading, ACPI, and SMP enabled. The 2.8 server won't stand for more than 5 days without crashing, and the 2.4 server was up 30 days crashed, now was up 12 days, and crashed. I didn't have a debugging kernel, I'll be building one when the datacenter reboots the server. I also don't have any panic messages.. I have, however, a few questions: - machdep.cpu_idle_hlt - I've seen a lot on google about this sysctl, but still don't fully understand it. What does this sysctl really changes? - HyperThreading - Do I really have a performance increase with HTT turned on? I've heard it can penalize performance because the scheduler isn't optimized for logical CPUs. Does having HTT enabled impacts the stability of the system? - ACPI - I'll be disabling ACPI along with HTT to see if the server doesn't crash for awhile. Is ACPI on 5.3-STABLE (around November 1st, it was pre-release) still a problem? Last but not the least, my 5.3-STABLE version is from a few days before the release. Since I had created a few jails by then, I didn't upgrade the system to use the -RELEASE. Was there any last-standing problem a few days before the release that could be causing my instability problems? Please share some common dual processor system knowledge, perhaps I'm missing something really obvious and making these servers unstable. Regards, Hugo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
HTT/SMP servers instability on 5.3-STABLE]
Hi, I have a Dual Xeon 2.4 and a Dual Xeon 2.8 servers running with HyperThreading, ACPI, and SMP enabled. The 2.8 server won't stand for more than 5 days without crashing, and the 2.4 server was up 30 days crashed, now was up 12 days, and crashed. I didn't have a debugging kernel, I'll be building one when the datacenter reboots the server. I also don't have any panic messages.. I have, however, a few questions: - machdep.cpu_idle_hlt - I've seen a lot on google about this sysctl, but still don't fully understand it. What does this sysctl really changes? - HyperThreading - Do I really have a performance increase with HTT turned on? I've heard it can penalize performance because the scheduler isn't optimized for logical CPUs. Does having HTT enabled impacts the stability of the system? - ACPI - I'll be disabling ACPI along with HTT to see if the server doesn't crash for awhile. Is ACPI on 5.3-STABLE (around November 1st, it was pre-release) still a problem? Last but not the least, my 5.3-STABLE version is from a few days before the release. Since I had created a few jails by then, I didn't upgrade the system to use the -RELEASE. Was there any last-standing problem a few days before the release that could be causing my instability problems? Please share some common dual processor system knowledge, perhaps I'm missing something really obvious and making these servers unstable. Regards, Hugo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: HTT/SMP servers instability on 5.3-STABLE]
On Dec 10, Toomas Aas launched this into the bitstream: Colin J. Raven wrote: On Dec 10, Toomas Aas launched this into the bitstream: For more than a month now, I've been running a Dual Xeon 2000 system (IBM eServer xSeries 225) with 5.3-RC2 and later upgraded to 5.3-RELEASE and I have no problems at all. Hyperthreading is disabled in BIOS, ACPI is enabled. Excuse me for jumping into this thread but could you elaborate as to why you have Nyperthreading disabled? I'm afraid I can't give you any good technical reasons. I simply think of HTT as Intel marketing blurb, meant to make you feel like you are getting two CPUs for the price of one. Well, actually it's still only one CPU. I've been running another single Xeon 2.4 box for more than a year. Initially, I ran several months with HTT enabled. Then I ran several months with HTT disabled. I didn't really notice any performance difference. Well thanks for sharing those observations. Until I read what you said I *assumed* that there was a performance difference with HTT enabled. The specs seem to show that there *is* a theoretical difference, yet clearly according to your observations there just isn't any difference of earth shaking proportions. Much appreciated! Regards, -Colin -- Colin J. Raven NetBSD on a Cobalt Qube2 - http://www.NetBSD.org - Fri Dec 10 19:56:00 UTC 2004 7:56PM up 4:09, 5 users, load averages: 1.11, 1.16, 1.16 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: HTT/SMP servers instability on 5.3-STABLE]
On Dec 10, Lucas Holt launched this into the bitstream: Well thanks for sharing those observations. Until I read what you said I *assumed* that there was a performance difference with HTT enabled. The specs seem to show that there *is* a theoretical difference, yet clearly according to your observations there just isn't any difference of earth shaking proportions. I've got a dual xeon 2.0 ghz workstation. I've tried running with and without HTT enabled on it. My observations were that it seemed to help slightly with certain tasks but in general degraded system performance. For example, if i build a world to upgrade the OS it takes at least 30 seconds longer with HTT enabled. I tried it multiple times to verify it. I even tried it with different values for the j flag. (3 4 5 and 6) Similarly, if i run it in windows with HTT enabled I noticed that windows was peppy but it was a disaster during gaming. Of course that makes sense as most of my games are not designed for multiple cpus. (enemy territory, quake 3, Doom 3, etc) I also realize i could play some of them in fbsd, except my radeon 9600 xt isn't supported for 3d acceleration! This is *most* surprising but extremely useful information, many thanks for taking the time to impart first hand experiences. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: HTT/SMP servers instability on 5.3-STABLE]
[EMAIL PROTECTED] wrote: Please share some common dual processor system knowledge, perhaps I'm missing something really obvious and making these servers unstable. For more than a month now, I've been running a Dual Xeon 2000 system (IBM eServer xSeries 225) with 5.3-RC2 and later upgraded to 5.3-RELEASE and I have no problems at all. Hyperthreading is disabled in BIOS, ACPI is enabled. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: HTT/SMP servers instability on 5.3-STABLE]
On Dec 10, Toomas Aas launched this into the bitstream: [EMAIL PROTECTED] wrote: Please share some common dual processor system knowledge, perhaps I'm missing something really obvious and making these servers unstable. For more than a month now, I've been running a Dual Xeon 2000 system (IBM eServer xSeries 225) with 5.3-RC2 and later upgraded to 5.3-RELEASE and I have no problems at all. Hyperthreading is disabled in BIOS, ACPI is enabled. Excuse me for jumping into this thread but could you elaborate as to why you have Nyperthreading disabled? We're about to run a dual cpu box ourselves so this is highly relevant (as well as just plain 'ol fascinating!!) Regards, -Colin -- Colin J. Raven NetBSD on a Cobalt Qube2 - http://www.NetBSD.org - Fri Dec 10 19:27:00 UTC 2004 7:27PM up 3:40, 5 users, load averages: 1.27, 1.18, 1.17 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: HTT/SMP servers instability on 5.3-STABLE]
Colin J. Raven wrote: On Dec 10, Toomas Aas launched this into the bitstream: For more than a month now, I've been running a Dual Xeon 2000 system (IBM eServer xSeries 225) with 5.3-RC2 and later upgraded to 5.3-RELEASE and I have no problems at all. Hyperthreading is disabled in BIOS, ACPI is enabled. Excuse me for jumping into this thread but could you elaborate as to why you have Nyperthreading disabled? I'm afraid I can't give you any good technical reasons. I simply think of HTT as Intel marketing blurb, meant to make you feel like you are getting two CPUs for the price of one. Well, actually it's still only one CPU. I've been running another single Xeon 2.4 box for more than a year. Initially, I ran several months with HTT enabled. Then I ran several months with HTT disabled. I didn't really notice any performance difference. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Fwd: HTT/SMP servers instability on 5.3-STABLE]
Well thanks for sharing those observations. Until I read what you said I *assumed* that there was a performance difference with HTT enabled. The specs seem to show that there *is* a theoretical difference, yet clearly according to your observations there just isn't any difference of earth shaking proportions. Much appreciated! Regards, -Colin -- Colin J. Raven NetBSD on a Cobalt Qube2 - http://www.NetBSD.org - Fri Dec 10 19:56:00 UTC 2004 7:56PM up 4:09, 5 users, load averages: 1.11, 1.16, 1.16 ___ I've got a dual xeon 2.0 ghz workstation. I've tried running with and without HTT enabled on it. My observations were that it seemed to help slightly with certain tasks but in general degraded system performance. For example, if i build a world to upgrade the OS it takes at least 30 seconds longer with HTT enabled. I tried it multiple times to verify it. I even tried it with different values for the j flag. (3 4 5 and 6) Similarly, if i run it in windows with HTT enabled I noticed that windows was peppy but it was a disaster during gaming. Of course that makes sense as most of my games are not designed for multiple cpus. (enemy territory, quake 3, Doom 3, etc) I also realize i could play some of them in fbsd, except my radeon 9600 xt isn't supported for 3d acceleration! Lucas Holt [EMAIL PROTECTED] FoolishGames.com (Jewel Fan Site) JustJournal.com (Free blogging) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
teamspeak server on 5.3-STABLE
installed teamspeak_server-2.0.19.40_1 from ports and when I start it up, the teamspeak sevrer starts, but the web admin interface does not. When I try to start the server manually as root, all It gives is monsterjam# /usr/local/lib/teamspeak_server/server_linux Error starting daemon. Aborted any idears? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: teamspeak server on 5.3-STABLE
On Thu, 9 Dec 2004 08:38:49 -0500, Jason wrote installed teamspeak_server-2.0.19.40_1 from ports and when I start it up, the teamspeak sevrer starts, but the web admin interface does not. When I try to start the server manually as root, all It gives is monsterjam# /usr/local/lib/teamspeak_server/server_linux Error starting daemon. Aborted any idears? Not sure about your problem, but AFAIK the sound driver is only capable of accepting requests from a single program only. So if you start a game and then teamspeak, teamspeak will not work. I've been playing around with this too, but I never managed to get it working. Correct me if I'm wrong though. Cheers, Jorn. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: teamspeak server on 5.3-STABLE
On Thu, 9 Dec 2004 08:38:49 -0500, Jason wrote installed teamspeak_server-2.0.19.40_1 from ports and when I start it up, the teamspeak sevrer starts, but the web admin interface does not. When I try to start the server manually as root, all It gives is monsterjam# /usr/local/lib/teamspeak_server/server_linux Error starting daemon. Aborted any idears? Not sure about your problem, but AFAIK the sound driver is only capable of accepting requests from a single program only. So if you start a game and then teamspeak, teamspeak will not work. I've been playing around with this too, but I never managed to get it working. Correct me if I'm wrong though. Jason is trying to install the teamspeak server, not the client. The server doesn't use sound output. It is possible to run the TeamSpeak *client* along with a game, if you're using a sound server, since it will mix the requests on its own (no more dsp device busy). On a side question, anyone knows why the mouse input on FreeBSD lags for some 0.6 secs while playing Wolfenstein? (and maybe other 3D, heavy resource games) It's annoying, since I use mouse1 to shoot and it's always delayed for about 0.6 seconds.. Nowdays I'm used to it, but if there is a way to get the old click-shoot behavior (like on Windows) it would be much, much better. Cheers, Jorn. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3 STABLE SMP Kernel
Hello all, I hope what I have is a simple question. I have a dual proc machine, that I have loaded 5.3 RELEASE on and then updated it to STABLE. While reading the Handbook I see where the GENERIC kernel has SMP built in via the SMP file in /usr/src/sys/i386/conf directory. So, to enable SMP for my custom kernel, do I simply need to edit SMP to include my custom kernel name? Thanks in advance, Ron Clark __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 STABLE SMP Kernel
Ronnie Clark wrote: Hello all, I hope what I have is a simple question. I have a dual proc machine, that I have loaded 5.3 RELEASE on and then updated it to STABLE. While reading the Handbook I see where the GENERIC kernel has SMP built in via the SMP file in /usr/src/sys/i386/conf directory. So, to enable SMP for my custom kernel, do I simply need to edit SMP to include my custom kernel name? From my kernel config: # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel device apic# I/O APIC Enjoy! =) Kind regards, Benjamin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FW: Installing gpsd on 5.3 STABLE
This was originally rejected by my office's mail filter. Had to resend from home. _ From: Steiger, N. Wilson GS-12(TRNG) ATG WESTPAC Sent: Thursday, December 02, 2004 2:23 PM To: '[EMAIL PROTECTED]' Subject: Installing gpsd on 5.3 STABLE Importance: High Trying to install gpsd-2.3 on a Dell Latitude CPi (400Mhz 128M RAM) FreeBSD 5.3-STABLE latest src ports cvsup'd. All ports upgraded and new kernel/userland installed. Trying to compile gpsd-2.3.running configure has no errors and tells me to then run make. I am not modifying the configure script in any way just simply ./configure. When running make or gmake it always fails with the following: make: if gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/X11R6/include -I/usr/X11R6/include -g -O2 -Wall -Werror -I/usr/X11R6/include -MT gps-gps.o -MD -MP -MF .deps/gps-gps.Tpo -c -o gps-gps.o `test -f 'gps.c' || echo './'`gps.c; then mv -f .deps/gps-gps.Tpo .deps/gps-gps.Po; else rm -f .deps/gps-gps.Tpo; exit 1; fi *** Error code 1 Stop in /root/install/gpsd-2.3. *** Error code 1 Stop in /root/install/gpsd-2.3. gmake: if gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/X11R6/include -I/usr/X11R6/include -g -O2 -Wall -Werror -I/usr/X11R6/include -MT gps-gps.o -MD -MP -MF .deps/gps-gps.Tpo -c -o gps-gps.o `test -f 'gps.c' || echo './'`gps.c; then mv -f .deps/gps-gps.Tpo .deps/gps-gps.Po; else rm -f .deps/gps-gps.Tpo; exit 1; fi *** Error code 1 Stop in /root/install/gpsd-2.3. *** Error code 1 Stop in /root/install/gpsd-2.3. I already installed the required LessTif then deinstalled it to install OpenMotif and I receive the same error regardless. I have attached all three full screen dumps and would appreciate anyone that could help. Kind Regards, Wilson Steiger Project Engineer IBFTC Training Specialist DRS Technical Services, Inc. make.gpsd.log Description: Binary data configure.gpsd.log Description: Binary data gmake.gpsd.screen Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems logging w/ IPF on FreeBSD 5.3-STABLE
On Mon, 29 Nov 2004 18:28:06 -0800, FMorales [EMAIL PROTECTED] wrote: bash-2.05b$ cat /etc/rc.conf | grep ip ipfilter_enable=YES ipfilter_rules=/etc/ipf.rules ipmon_enable=YES ipmon_flags=-Ds change the above to read something along the lines of: ipmon_flags=-Dn /var/log/ipfilter.log remove the s in other words and put in the path to your log file to output the data. nelis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems logging w/ IPF on FreeBSD 5.3-STABLE
Hello all i recently installed FreeBSD 5.3 and am so far extremely pleased with it. I read the section in the handbook that discussed setting up IPF w/ FreeBSD 5.x, and also how to turn on logging and such. Well IPF works perfectly, however my logging is NOT going where it's supposed to. I used the same files the tutorial did, that is: /var/log/ipfilter.log etc... I only log for the block rules, however the data that's supposed to be written to my log file is NOT being written there at all. My messages seem to be written to: /var/log/security and /var/log/messages instead of /var/log/ipfilter.log. The important thing is i found where things are being logged, however i was so stoked to get everything setup and running, then this problem. Now it's just a matter of principle and seeing where i went wrong. I offer the following list of configuration settings, and information about my current setup and system. If anyone needs more information please ask i will be more than happy to provide it. Any help or a point in the right direction would be greatly appreciated. I'm sure it's something very silly i've done and am just overlooking. Thanks in advance all. FMorales... System: FreeBSD 5.3-RELEASE AMD Athlon XP 1600+ 512MB RAM -- Alright lets run down the list, first things first. I decided -- to recompile my kernel w/ the needed options to actually build -- IPF etc.. into the kernel. I used a simple config named Test -- here is the output showing the needed 'options' are there: bash-2.05b$ cat /usr/src/sys/i386/conf/Test | grep IPFILTER | head -3 options IPFILTER options IPFILTER_LOG options IPFILTER_DEFAULT_BLOCK -- How i built, and installed the kernel were as follows: bash-2.05b$ cd /usr/src bash-2.05b$ make buildkernel KERNCONF=Test bash-2.05b$ make installkernel KERNCONF=Test -- After which i rebooted, and everything went ok. -- Next we make sure we're running the correct kernel: bash-2.05b$ uname -i Test -- Lets make sure our log file exists: bash-2.05b$ ls -la /var/log/ipfil* -rw-r--r-- 1 root wheel 0 Nov 27 14:29 /var/log/ipfilter.log -- Ok lets be sure we added the needed options to /etc/rc.conf : bash-2.05b$ cat /etc/rc.conf | grep ip ipfilter_enable=YES ipfilter_rules=/etc/ipf.rules ipmon_enable=YES ipmon_flags=-Ds -- Lets make sure we have the correct values in /etc/syslog.conf: bash-2.05b$ cat /etc/syslog.conf | grep local local0.*/var/log/ipfilter.log -- This entry is the FIRST one in /etc/syslog.conf. (NOTE: Using -- local0.* OR Local0.* has no effect on the outcome) -- We also told it to rotate our logs everyday at midnight: bash-2.05b$ cat /etc/newsyslog.conf | grep ipfilter /var/log/ipfilter.log 600 15*$D0 JN Ok all config looked ok. Next i remembered to restart syslogd. I first did it with: kill -HUP pid after getting a valid pid. I have ALSO rebooted several times just incase, no dice. Next i read the syslogd manpage and restarted syslogd using: syslogd -s -v -v to get verbose logging. As i said before it DOES log to both /var/log/security and /var/log/messages Now the output from a blocked packet was this: (I block telnet both ways so when i try to telnet this is what gets written) Nov 29 17:47:01 security.warn altf2o ipmon[177]: 17:47:00.419095 rl0 @0:19 b x.x.x.x,62902 - z.z.z.z,23 So it's apparent security.* in /etc/syslog.conf is picking it up, but i'm not sure why if it should be comming in to 'syslogd' as local0.* according to the Handbook. (Note: The output in BOTH /var/log/security and /var/log/messages is identical) Lastely we check 'ipmon' to be sure it's started and with the correct options: bash-2.05b$ ps -aux | grep ipmon | head -1 root 177 0.0 0.3 1856 1400 ?? Ss 5:52PM 0:00.01 ipmon -Ds *whew* That's it, hopefully that's enough for someone to spot my (i'm sure silly) mistake. Thanks again all... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-STABLE - system after few hours
On Tue, Nov 23, 2004 at 10:02:19AM -0600, Dan Nelson wrote: Enable crashdumps by setting dumpdev=/path/to/swap/slice in rc.conf, wait for the system to crash again, then use the dump to get a stack trace, and post that. http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING here it is: discordia# kgdb /boot/kernel/kernel /var/crash/vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd. (no debugging symbols found)...0xc04e8cc6 in doadump () (kgdb) where #0 0xc04e8cc6 in doadump () #1 0xc04e92bf in boot () #2 0xc04e95e5 in panic () #3 0xc05f29a0 in trap_fatal () #4 0xc05f26e3 in trap_pfault () #5 0xc05f233d in trap () #6 0xc05e0f4a in calltrap () #7 0xc04d0018 in do_execve () #8 0xc0517b85 in ttwakeup () #9 0xc05167e8 in ttymodem () #10 0xc051a4d3 in ptcopen () #11 0xc04b16de in spec_open () #12 0xc04b1423 in spec_vnoperate () #13 0xc0547511 in vn_open_cred () #14 0xc05470f6 in vn_open () #15 0xc054120f in kern_open () #16 0xc0541128 in open () #17 0xc05f2cab in syscall () #18 0xc05e0f9f in Xint0x80_syscall () #19 0x002f in ?? () #20 0x002f in ?? () #21 0x002f in ?? () #22 0x in ?? () #23 0x281ddc2d in ?? () #24 0xbfbfe4c8 in ?? () #25 0xea4e2d74 in ?? () #26 0x281df860 in ?? () #27 0x281ddc4b in ?? () #28 0x283415ec in ?? () #29 0x0005 in ?? () #30 0x000c in ?? () #31 0x0002 in ?? () #32 0x282ca517 in ?? () #33 0x001f in ?? () #34 0x0292 in ?? () #35 0xbfbfe46c in ?? () #36 0x002f in ?? () #37 0x2072746f in ?? () #38 0x70796e47 in ?? () #39 0x6f682f00 in ?? () #40 0x742f656d in ?? () #41 0x2fb6d000 in ?? () #42 0xc2a7 in ?? () #43 0xc2a054b0 in ?? () #44 0xea4e2aac in ?? () #45 0xea4e2a94 in ?? () #46 0xc1c404b0 in ?? () #47 0xc04f98c7 in sched_switch () Previous frame inner to this frame (corrupt stack?) pgp3r43yeP4zQ.pgp Description: PGP signature
Re: 5.3-STABLE - system after few hours
On Tue, Nov 23, 2004 at 10:02:19AM -0600, Dan Nelson wrote: Enable crashdumps by setting dumpdev=/path/to/swap/slice in rc.conf, wait for the system to crash again, then use the dump to get a stack trace, and post that. http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING here it is: discordia# kgdb /boot/kernel/kernel /var/crash/vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd. (no debugging symbols found)...0xc04e8cc6 in doadump () (kgdb) where #0 0xc04e8cc6 in doadump () #1 0xc04e92bf in boot () #2 0xc04e95e5 in panic () #3 0xc05f29a0 in trap_fatal () #4 0xc05f26e3 in trap_pfault () #5 0xc05f233d in trap () #6 0xc05e0f4a in calltrap () #7 0xc04d0018 in do_execve () #8 0xc0517b85 in ttwakeup () #9 0xc05167e8 in ttymodem () #10 0xc051a4d3 in ptcopen () #11 0xc04b16de in spec_open () #12 0xc04b1423 in spec_vnoperate () #13 0xc0547511 in vn_open_cred () #14 0xc05470f6 in vn_open () #15 0xc054120f in kern_open () #16 0xc0541128 in open () #17 0xc05f2cab in syscall () #18 0xc05e0f9f in Xint0x80_syscall () #19 0x002f in ?? () #20 0x002f in ?? () #21 0x002f in ?? () #22 0x in ?? () #23 0x281ddc2d in ?? () #24 0xbfbfe4c8 in ?? () #25 0xea4e2d74 in ?? () #26 0x281df860 in ?? () #27 0x281ddc4b in ?? () #28 0x283415ec in ?? () #29 0x0005 in ?? () #30 0x000c in ?? () #31 0x0002 in ?? () #32 0x282ca517 in ?? () #33 0x001f in ?? () #34 0x0292 in ?? () #35 0xbfbfe46c in ?? () #36 0x002f in ?? () #37 0x2072746f in ?? () #38 0x70796e47 in ?? () #39 0x6f682f00 in ?? () #40 0x742f656d in ?? () #41 0x2fb6d000 in ?? () #42 0xc2a7 in ?? () #43 0xc2a054b0 in ?? () #44 0xea4e2aac in ?? () #45 0xea4e2a94 in ?? () #46 0xc1c404b0 in ?? () #47 0xc04f98c7 in sched_switch () Previous frame inner to this frame (corrupt stack?) pgpMPeyEFBOFa.pgp Description: PGP signature
5.3-STABLE - system after few hours
Hi, after upgrade from 5.2.1 o 5.3-STABLE my system started to reboot on regular basis. The error message on screen (not always showing): Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id=03 fault virtual address = 0x1c fault code = supervisor write, page not present instruction pointer = 0x8:0xc04ce84b stack pointer = 0x10:0xea54f9co frame pointer = 0x10:0xea54f9cc code segment = base 0x0, limit 0xf type 0x1b = DPL 0, pres 1, def32 1 , gran 1 procesor eflags = interrupt cenabled, resume, IOPL=0 current process = 11445 (screen) trap number = 12 panic: page fault cpuid = 0 boot() called on cpu#0 [14:16] [EMAIL PROTECTED]:~ uname -r 5.3-STABLE [14:16] [EMAIL PROTECTED]:~ pkg_info | grep screen screen-4.0.2_1 A multi-screen window manager system has been tested with memtest and cpuburn - no errors were detected. Please advice. -- pgpxLjPfttVZU.pgp Description: PGP signature
Re: 5.3-STABLE - system after few hours
Piotr Gnyp wrote: Hi, after upgrade from 5.2.1 o 5.3-STABLE my system started to reboot on regular basis. The error message on screen (not always showing): Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id=03 fault virtual address = 0x1c fault code = supervisor write, page not present instruction pointer = 0x8:0xc04ce84b stack pointer = 0x10:0xea54f9co frame pointer = 0x10:0xea54f9cc code segment = base 0x0, limit 0xf type 0x1b = DPL 0, pres 1, def32 1 , gran 1 procesor eflags = interrupt cenabled, resume, IOPL=0 current process = 11445 (screen) trap number = 12 panic: page fault cpuid = 0 boot() called on cpu#0 [14:16] [EMAIL PROTECTED]:~ uname -r 5.3-STABLE [14:16] [EMAIL PROTECTED]:~ pkg_info | grep screen screen-4.0.2_1 A multi-screen window manager system has been tested with memtest and cpuburn - no errors were detected. Please advice. The first problem is your trying to run 5.3-STABLE. the -STABLE tag does NOT mean the system will be stable it mean the code base is relatively stable compared to -CURRENT. Until FreeBSD 5.x matures a bit more (maybe after 5.5-Release) normal users should NOT be tracking -STABLE. Change your cvsup-supfile to RELENG_5_3, cvsup to 5.3-RELEASE-p1, and rebuild your system. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-STABLE - system after few hours
On Tue, Nov 23, 2004 at 09:06:44AM -0600, Nikolas Britton wrote: The first problem is your trying to run 5.3-STABLE. the -STABLE tag does NOT mean the system will be stable it mean the code base is relatively stable compared to -CURRENT. Until FreeBSD 5.x matures a bit more (maybe after 5.5-Release) normal users should NOT be tracking -STABLE. Change your cvsup-supfile to RELENG_5_3, cvsup to 5.3-RELEASE-p1, and rebuild your system. I`ve just migrated from 5.3-RELEASE. Same thing happened there. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-STABLE - system after few hours
Piotr Gnyp wrote: On Tue, Nov 23, 2004 at 09:06:44AM -0600, Nikolas Britton wrote: The first problem is your trying to run 5.3-STABLE. the -STABLE tag does NOT mean the system will be stable it mean the code base is relatively stable compared to -CURRENT. Until FreeBSD 5.x matures a bit more (maybe after 5.5-Release) normal users should NOT be tracking -STABLE. Change your cvsup-supfile to RELENG_5_3, cvsup to 5.3-RELEASE-p1, and rebuild your system. I`ve just migrated from 5.3-RELEASE. Same thing happened there. you rebuild your ports (screen) after you updated from 5.2.1? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-STABLE - system after few hours
On Tue, Nov 23, 2004 at 09:38:50AM -0600, Nikolas Britton wrote: you rebuild your ports (screen) after you updated from 5.2.1? Yes. In fact, i did it again a while ago. I`ll check if the error will occur again. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-STABLE - system after few hours
In the last episode (Nov 23), Piotr Gnyp said: after upgrade from 5.2.1 o 5.3-STABLE my system started to reboot on regular basis. The error message on screen (not always showing): Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id=03 fault virtual address = 0x1c fault code = supervisor write, page not present instruction pointer = 0x8:0xc04ce84b stack pointer = 0x10:0xea54f9co frame pointer = 0x10:0xea54f9cc code segment = base 0x0, limit 0xf type 0x1b = DPL 0, pres 1, def32 1 , gran 1 procesor eflags = interrupt cenabled, resume, IOPL=0 current process = 11445 (screen) trap number = 12 panic: page fault cpuid = 0 boot() called on cpu#0 Enable crashdumps by setting dumpdev=/path/to/swap/slice in rc.conf, wait for the system to crash again, then use the dump to get a stack trace, and post that. http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ohphone 1.4.1 FreeBSD 5.3 Stable
Hello, anybody there has tried ohphone 1.4.1 in FreeBSD 5.3 Stable? I have working sound (output good. Input, well the mic records sound, not good quality). Ophone registers to gatekeeper, but no sound is produced while a call is in course. Error messages are generated by PCM channel.c. However, other applications uses /dev/dsp and works well. The mic records poor quality sound... did not dig into it yet. Thanks hardware: Toshiba Satellite 2805-S302 % sysctl -a | grep snd hw.snd.targetirqrate: 32 hw.snd.report_soft_formats: 1 hw.snd.verbose: 1 hw.snd.unit: 0 hw.snd.maxautovchans: 4 hw.snd.pcm0.buffersize: 4096 hw.snd.pcm0.vchans: 4 % mixer Mixer vol is currently set to 71:71 Mixer pcm is currently set to 75:75 Mixer line is currently set to 75:75 Mixer mic is currently set to 75:75 Mixer cd is currently set to 75:75 Mixer rec is currently set to 75:75 Recording source: mic error messages: Nov 23 20:33:29 kernel: Danger! pcm0:play:3 bufsoft size increasing from 3584 to 3956 after CHANNEL_SETBLOCKSIZE() Nov 23 20:33:29 kernel: Danger! pcm0:record:1 bufsoft size increasing from 3584 to 4048 after CHANNEL_SETBLOCKSIZE() Nov 23 20:33:29 kernel: Danger! pcm0:play:3 bufsoft size increasing from 3584 to 3956 after CHANNEL_SETBLOCKSIZE() Nov 23 20:33:29 kernel: Danger! pcm0:record:1 bufsoft size increasing from 3584 to 4048 after CHANNEL_SETBLOCKSIZE() Nov 23 20:33:29 kernel: Danger! pcm0:play:3 bufsoft size increasing from 3584 to 3956 after CHANNEL_SETBLOCKSIZE() Nov 23 20:33:29 kernel: Danger! pcm0:record:1 bufsoft size increasing from 3584 to 4048 after CHANNEL_SETBLOCKSIZE() Nov 23 20:33:30 kernel: pcm0:play:3: play interrupt timeout, ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvups with 5.3 stable
On Wednesday 17 November 2004 05:31 pm, [EMAIL PROTECTED] wrote: Has anyone got cvsup to sucessfully update their ports collection? When I run cvsup, with tag=RELENG_5_3, cvsup just deletes everything in /usr/ports. I replaced the ports collection with the full port tarball from the ports collection search page. Cvsup deletes that as well. I am using the ports-supfile from examples, and have only change the cvsup host. Has anyone else experience this? The only version of ports and that tag for ports is tag=.. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvups with 5.3 stable
On Thu, Nov 18, 2004 at 01:31:23AM +, [EMAIL PROTECTED] wrote: Has anyone got cvsup to sucessfully update their ports collection? When I run cvsup, with tag=RELENG_5_3, cvsup just deletes everything in /usr/ports. I replaced the ports collection with the full port tarball from the ports collection search page. Cvsup deletes that as well. I am using the ports-supfile from examples, and have only change the cvsup host. Has anyone else experience this? 1) Wrap your lines at 70 characters, please. 2) This is a FAQ; ports aren't branched, so don't use a branch tag. If you were truly using the example ports-supfile you'd not have a branch tag :-) Kris pgpugtJj3tEG6.pgp Description: PGP signature
Re: cvups with 5.3 stable
[EMAIL PROTECTED] wrote: Has anyone got cvsup to sucessfully update their ports collection? When I run cvsup, with tag=RELENG_5_3, cvsup just deletes everything in /usr/ports. I replaced the ports collection with the full port tarball from the ports collection search page. Cvsup deletes that as well. I am using the ports-supfile from examples, and have only change the cvsup host. Has anyone else experience this? Casey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] To CVSup the ports - the ports-supfile ought to look like this: *default host=cvsup2.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix ports-all What you seem to be doing is CVSuping the src tree. I think your confused a bite - here's the lines for src: (STABLE) *default host=cvsup2.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5 *default delete use-rel-suffix *default compress src-all -- Best regards, Chris Laugh and the world laughs with you. cry and ... you have to blow your nose. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
