make buildworld error in libpam/modules/pam_ssh
I'm experiencing the following error while bulding world: ===> libpam/modules/pam_ssh cc -nostdinc -O -pipe -I/usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh -I/usr/src/lib/libpam/modules/pam_ssh/../../../../contrib/libpam/libpam/include -I/usr/src/lib/libpam/modules/pam_ssh/../../libpam -I/usr/obj/usr/src/i386/usr/include -Werror -Wall -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c -o pam_ssh.o cc1: warnings being treated as errors In file included from /usr/obj/usr/src/i386/usr/include/openssl/evp.h:129, from /usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c:63: /usr/obj/usr/src/i386/usr/include/openssl/rsa.h:218: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/rsa.h:219: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/rsa.h:220: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/rsa.h:222: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/rsa.h:223: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/rsa.h:226: warning: function declaration isn't a prototype In file included from /usr/obj/usr/src/i386/usr/include/openssl/objects.h:960, from /usr/obj/usr/src/i386/usr/include/openssl/evp.h:140, from /usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c:63: /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:377: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:378: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:379: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:380: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:753: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:755: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:806: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:806: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:809: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:809: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:810: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:817: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:817: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:818: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:852: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:854: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:856: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/asn1.h:857: warning: function declaration isn't a prototype In file included from /usr/src/lib/libpam/modules/pam_ssh/pam_ssh.c:63: /usr/obj/usr/src/i386/usr/include/openssl/evp.h:269: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/evp.h:270: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/evp.h:271: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/evp.h:273: warning: function declaration isn't a prototype /usr/obj/usr/src/i386/usr/include/openssl/evp.h:274: warning: function declaration isn't a prototype *** Error code 1 Stop in /usr/src/lib/libpam/modules/pam_ssh. *** Error code 1 Stop in /usr/src/lib/libpam/modules. *** Error code 1 Stop in /usr/src/lib/libpam. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
usb mouse won't work
FreeBSD does not want to work with my USB mouse. I believe it to be a problem with the motherboard, a Tyan S1834. The mouse does work under BeOS and Windows so I know it's not toast. Also, the mouse works with FreeBSD on my Tyan S1832 motherboard so that's a good sign too. Here's my kernel output: Feb 4 20:51:54 max syslogd: kernel boot file is /boot/kernel/kernel Feb 4 20:51:54 max kernel: Copyright (c) 1992-2002 The FreeBSD Project. Feb 4 20:51:54 max kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Feb 4 20:51:54 max kernel: The Regents of the University of California. All rights reserved. Feb 4 20:51:54 max kernel: FreeBSD 5.0-CURRENT #1: Mon Feb 4 20:32:50 CST 2002 Feb 4 20:51:54 max kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MAXKERNEL Feb 4 20:51:54 max kernel: Preloaded elf kernel "/boot/kernel/kernel" at 0xc040. Feb 4 20:51:54 max kernel: Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04000a8. Feb 4 20:51:54 max kernel: Timecounter "i8254" frequency 1193182 Hz Feb 4 20:51:54 max kernel: CPU: Pentium III/Pentium III Xeon/Celeron (933.03-MHz 686-class CPU) Feb 4 20:51:54 max kernel: Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Feb 4 20:51:54 max kernel: Features=0x383fbff Feb 4 20:51:54 max kernel: real memory = 402587648 (393152K bytes) Feb 4 20:51:54 max kernel: avail memory = 387457024 (378376K bytes) Feb 4 20:51:54 max kernel: Programming 24 pins in IOAPIC #0 Feb 4 20:51:54 max kernel: IOAPIC #0 intpin 2 -> irq 0 Feb 4 20:51:54 max kernel: IOAPIC #0 intpin 16 -> irq 12 Feb 4 20:51:54 max kernel: IOAPIC #0 intpin 17 -> irq 10 Feb 4 20:51:54 max kernel: IOAPIC #0 intpin 19 -> irq 11 Feb 4 20:51:54 max kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Feb 4 20:51:54 max kernel: cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 Feb 4 20:51:54 max kernel: cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 Feb 4 20:51:54 max kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Feb 4 20:51:54 max kernel: Pentium Pro MTRR support enabled Feb 4 20:51:54 max kernel: Using $PIR table, 8 entries at 0xc00fdb50 Feb 4 20:51:54 max kernel: npx0: on motherboard Feb 4 20:51:55 max kernel: npx0: INT 16 interface Feb 4 20:51:55 max kernel: acpi0: on motherboard Feb 4 20:51:55 max kernel: acpi0: power button is handled as a fixed feature programming model. Feb 4 20:51:55 max kernel: Timecounter "ACPI" frequency 3579545 Hz Feb 4 20:51:55 max kernel: ACPI-0294: *** Error: Method execution failed, AE_AML_UNINITIALIZED_LOCAL Feb 4 20:51:55 max kernel: can't fetch resources for \_SB_.PCI0.FDC0 - AE_AML_UNINITIALIZED_LOCAL Feb 4 20:51:55 max kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 Feb 4 20:51:55 max kernel: acpi_cpu0: on acpi0 Feb 4 20:51:55 max kernel: acpi_cpu1: on acpi0 Feb 4 20:51:55 max kernel: acpi_button0: on acpi0 Feb 4 20:51:55 max kernel: acpi_pcib0: port 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 Feb 4 20:51:55 max kernel: pci0: on acpi_pcib0 Feb 4 20:51:55 max kernel: agp0: mem 0xe000-0xe3ff at device 0.0 on pci0 Feb 4 20:51:55 max kernel: pcib1: at device 1.0 on pci0 Feb 4 20:51:55 max kernel: pci1: on pcib1 Feb 4 20:51:55 max kernel: pci1: at device 0.0 (no driver attached) Feb 4 20:51:55 max kernel: isab0: at device 7.0 on pci0 Feb 4 20:51:55 max kernel: isa0: on isab0 Feb 4 20:51:55 max kernel: atapci0: port 0xd000-0xd00f at device 7.1 on pci0 Feb 4 20:51:55 max kernel: ata0: at 0x1f0 irq 14 on atapci0 Feb 4 20:51:55 max kernel: ata1: at 0x170 irq 15 on atapci0 Feb 4 20:51:55 max kernel: uhci0: port 0xd400-0xd41f irq 11 at device 7.2 on pci0 Feb 4 20:51:55 max kernel: usb0: on uhci0 Feb 4 20:51:55 max kernel: usb0: USB revision 1.0 Feb 4 20:51:55 max kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Feb 4 20:51:55 max kernel: uhub0: 2 ports with 2 removable, self powered Feb 4 20:51:55 max kernel: ums0: Logitech USB-PS/2 Mouse, rev 1.00/1.20, addr 2, iclass 3/1 Feb 4 20:51:55 max kernel: ums0: 3 buttons Feb 4 20:51:55 max kernel: ums_attach: sc=0xc1eb0400 Feb 4 20:51:55 max kernel: ums_attach: X 8/8 Feb 4 20:51:55 max kernel: ums_attach: Y 16/8 Feb 4 20:51:55 max kernel: ums_attach: B1 0/1 Feb 4 20:51:55 max kernel: ums_attach: B2 1/1 Feb 4 20:51:55 max kernel: ums_attach: B3 2/1 Feb 4 20:51:55 max kernel: ums_attach: size=3, id=0 Feb 4 20:51:55 max kernel: uscanner0: Hewlett Packard Hewlett Packard ScanJet 5300C, rev 1.00/0.01, addr 3 Feb 4 20:51:55 max kernel: ahc0: port 0xd800-0xd8ff mem 0xe5101000-0xe5101fff irq 11 at device 15.0 on pci0 Feb 4 20:51:55 max kernel: aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/255 SCBs Feb 4 20:51:55 max kernel: fxp0: port 0xdc00-0xdc1f mem 0xe500-0xe50f,0xe510-0xe51 00fff irq 10 at device 17.0 on pci0 Feb 4 20:51:55 max kernel: fxp0: E
Re: ports/34908: libpng port makes bad dynamic library on -CURRENT
David O'Brien wrote: > This is not much of a bug report. Was libpng compiled with new binuils > or old? Someone that is having problems (which I am not), needs to > compile things with -g, not strip them, use gdb and provide a REAL bug > report. > In /etc/make.conf I have: CFLAGS= -O0 -g -pipe COPTFLAGS= -O0 -g -pipe Now how can I prevent all stripping and what commands should I use with gdb to get you the info you need? Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ports/34908: libpng port makes bad dynamic library on -CURRENT
Alexander N. Kabaev wrote: >> Interesting. Is the DF_TEXTREL flag set in DT_FLAGS instead? Is the >> library linked w/ -enable-new-dtags? Are the new dtags enabled by >> default in the new binutils? Someting in elf32.em? > > No. DT_FLAGS entry is not created regardless of whether the > --enable-new-dtags parameter has been passed to the linker. Ld simply > ignores dynamic relocation entries for local symbols while checking > whether either DT_FLAGS or DT_TEXTREL should be created. Attached patch > appears to fix the problem for me and has not caused any problems on my > test box so far but I am not making any claims about its correctness. > Use on your own risk. > It's got to be at least partially correct because this patch does indeed work. I've been punishing my machine and it's doing great! Thank you, Alexander, and all. Pete... >> Are the new dtags enabled by default in the new binutils? > > No, it seems like the new dtags are disabled by default. > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
problem installing ports
Hi, Two ports I've tried to install recently, open-motif-devel and AbiWord, have attempted to `mkdir /'. This fails with: "mkdir: /: Is a directory." Installing these ports works just fine under 4.5-STABLE. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ports/34908: libpng port makes bad dynamic library on -CURRENT
Michael D. Harnois wrote: > On Thu, 2002-02-21 at 04:03, David O'Brien wrote: > > >>On Thu, Feb 21, 2002 at 12:05:31AM +0100, Stijn Hoop wrote: >> >>>Maybe this can now be committed? >>> >>NOT until I have sufficient feedback from the FSF Binutils developers. >> > > OK, I'm confused. binutils has been broken for three weeks. We have a > patch that we know fixes, at the very least, one of the known roblems. > However, it can't be committed without feedback from the developers. > > So having binutils broken indefinitely is better than applying a patch > that *might* have to be backed out or altered later? > I would like to wait and see what David comes up with. I've applied the patch and things work for the most part, but there are some problems I'm having with the vim, open-motif-devel and AbiWord ports that I did not see until this patch. So I guess the lesson is that if you want to run -CURRENT you just have to roll with the punches. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ports problem: where to start
I just upgraded everything on my system and I'm still having trouble with vim, AbiWord, and open-motif-devel. The problem with vim is one I can fix by changing the install.sh script it comes with by forcing it to link against the X11 library. For some reason it does not pick up that it's required: $ gvim /usr/libexec/ld-elf.so.1: Shared object "libXThrStub.XmbResetIC" not found The other two are executing `mkdir /' at install time. This fails: ===> Installing for AbiWord-0.99.1_1 ===> AbiWord-0.99.1_1 depends on shared library: png.5 - found ===> AbiWord-0.99.1_1 depends on shared library: giconv.2 - found ===> AbiWord-0.99.1_1 depends on shared library: psiconv.7 - found ===> AbiWord-0.99.1_1 depends on shared library: X11.6 - found ===> AbiWord-0.99.1_1 depends on shared library: glib12.3 - found ===> AbiWord-0.99.1_1 depends on shared library: gtk12.2 - found Making install in src gmake[1]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src' Making install in tools gmake[2]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools' Making install in cdump gmake[3]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' Making install in xp gmake[4]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump/xp' gmake[5]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump/xp' gmake[5]: Nothing to be done for `install-exec-am'. gmake[5]: Nothing to be done for `install-data-am'. gmake[5]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump/xp' gmake[4]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump/xp' gmake[4]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' gmake[5]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' gmake[5]: Nothing to be done for `install-exec-am'. gmake[5]: Nothing to be done for `install-data-am'. gmake[5]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' gmake[4]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' gmake[3]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' Making install in pfa2afm gmake[3]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' Making install in unix gmake[4]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm/unix' gmake[5]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm/unix' gmake[5]: Nothing to be done for `install-exec-am'. gmake[5]: Nothing to be done for `install-data-am'. gmake[5]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm/unix' gmake[4]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm/unix' gmake[4]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' gmake[5]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' gmake[5]: Nothing to be done for `install-exec-am'. gmake[5]: Nothing to be done for `install-data-am'. gmake[5]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' gmake[4]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' gmake[3]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' Making install in ttftool gmake[3]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool' Making install in unix gmake[4]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool/unix' gmake[5]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool/unix' mkdir: /: Is a directory gmake[5]: *** [install-exec-local] Error 1 gmake[5]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool/unix' gmake[4]: *** [install-am] Error 2 gmake[4]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool/unix' gmake[3]: *** [install-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool' gmake[2]: *** [install-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools' gmake[1]: *** [install-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src' gmake: *** [install-recursive] Error 1 *** Error code 2 Stop in /usr/ports/editors/AbiWord. *** Error code 1 Stop in /usr/ports/editors/AbiWord. *** Error code 1 Stop in /usr/ports/editors/AbiWord. *** Error code 1 Stop in /usr/ports/editors/AbiWord. ===> Installing for open-motif-devel-2.1.30 ===> open-motif-devel-2.1.30 depends on shared library: X11.6 - found mkdir: /: Is a directory *** Error code 1 Stop in /usr/ports/x11-toolkits/open-motif-devel. *** Error
Re: ** HEADS UP **
On Mon, Mar 12, 2001 at 05:52:00PM -0600, Jonathan Lemon wrote: > I committed a miibus'ified fxp driver to the tree today, and made > it the default. If you compile fxp into your kernel statically, > you will also need "device miibus" as well, if it isn't there already. > > If you notice any problems with the driver (things that were working > and are not working now), please let me know. If you happend to have > a chip that did _NOT_ work but now DOES work, please boot the machine > with -v, and send me the line that says "PCI IDs:". > > If you have a fxp device that still doesn't work, then please get > in touch with me (and send the output of the line above). > -- > Jonathan > Hi Jonathan, I've got a slight problem in that it is not correctly auto detecting the media type. It should be setting itself to 10baseT/UTP. I'm running DHCP on my -current machine and I'm not sure how to set it so that it configures the interface correctly. It previously "just worked" without any special media settings. Is there something I can provide to help correct this? Thanks, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
usr.sbin/ntp/ntpd make: Cannot allocate memory
Hi, I'm new at tracking current and I'm having trouble getting past this make error. I've searched around the archive but can't find the answer. I have 128MB of memory and 384MB of swap so I'm really not sure what's going on. I'm running a tyan s1832dl with dual PII350s and SMP seems to be working fine everywhere else so I don't think it's that. Heck, I even got my sound card to make noise. Anyone want to help this newbie? Thanks, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
debug build of libc_r
Hi, I'm seeing a crash related to libc_r. Could someone please instruct me as to how to build a debug version. Thanks, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gcc-devel and 5.0-current
Hi, Just wondering if anyone has gotten make world to work with this combo. It is expected that gcc 3.0 will become the default compiler for FreeBSD 5.0? Thanks, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel panic
I get this when I try to enable bridging:
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:232
#1 0xc01f5f8e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:364
#2 0xc01f61d3 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#3 0xc0239317 in bremfree (bp=0xcae72988) at
/usr/src/sys/kern/vfs_bio.c:634
#4 0xc023bd20 in getblk (vp=0xc33e5000, blkno=8652544, size=16384,
slpflag=0,
slptimeo=0) at /usr/src/sys/kern/vfs_bio.c:2364
#5 0xc023944a in breadn (vp=0xc33e5000, blkno=0, size=0, rablkno=0x0,
rabsize=0x0, cnt=0, cred=0x0, bpp=0x0) at
/usr/src/sys/kern/vfs_bio.c:692
#6 0xc02393fc in bread (vp=0x0, blkno=0, size=0, cred=0x0, bpp=0x0)
at /usr/src/sys/kern/vfs_bio.c:674
#7 0xc02a7d03 in ffs_update (vp=0xc33e4000, waitfor=0)
at /usr/src/sys/ufs/ffs/ffs_inode.c:102
#8 0xc02bbf1f in ffs_fsync (ap=0xd2c09278)
at /usr/src/sys/ufs/ffs/ffs_vnops.c:315
#9 0xc02bb0ee in ffs_sync (mp=0xc33ce600, waitfor=2, cred=0xc11dfe80,
td=0xc037a700) at vnode_if.h:612
#10 0xc024d36b in sync (td=0xc037a700, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:138
#11 0xc01f5b9c in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:273
#12 0xc01f61d3 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#13 0xc0218424 in witness_lock (lock=0xc03873a0, flags=8,
file=0xc0357d23 "/usr/src/sys/net/if.c", line=890)
at /usr/src/sys/kern/subr_witness.c:614
#14 0xc01ec5c1 in _mtx_lock_flags (m=0xc037ed40, opts=0,
file=0xc03873a0 "@í7À\035}5À\035}5À", line=-1069726564)
at /usr/src/sys/kern/kern_mutex.c:328
#15 0xc025b270 in ifa_ifwithdstaddr (addr=0xc03873a0)
at /usr/src/sys/net/if.c:890
#16 0xc0262680 in ifa_ifwithroute (flags=0, dst=0xc33ce0c0,
gateway=0xc33ce0c0)
at /usr/src/sys/net/route.c:423
#17 0xc0262847 in rt_getifa (info=0xc33ce0c0) at
/usr/src/sys/net/route.c:520
#18 0xc0262ad1 in rtrequest1 (req=1, info=0xd2c09460, ret_nrt=0xd2c094b4)
at /usr/src/sys/net/route.c:632
#19 0xc026276b in rtrequest (req=0, dst=0x0, gateway=0x0, netmask=0x0,
flags=0, ret_nrt=0x0) at /usr/src/sys/net/route.c:479
#20 0xc0282dd7 in in6_ifloop_request (cmd=1, ifa=0xc33ce000)
at /usr/src/sys/netinet6/in6.c:167
#21 0xc0282fce in in6_ifaddloop (ifa=0xc33ce000)
at /usr/src/sys/netinet6/in6.c:224
#22 0xc0285327 in in6_ifinit (ifp=0xc32f4800, ia=0x0, sin6=0x0, newhost=1)
at /usr/src/sys/netinet6/in6.c:1634
#23 0xc028422d in in6_update_ifa (ifp=0xc32f4800, ifra=0xd2c09668,
ia=0xc33ce000) at /usr/src/sys/netinet6/in6.c:978
#24 0xc0287514 in in6_ifattach_linklocal (ifp=0xd2c09668, altifp=0x0)
at /usr/src/sys/netinet6/in6_ifattach.c:497
#25 0xc0287e18 in in6_ifattach (ifp=0xc33ce000, altifp=0x0)
#26 0xc0285e2b in in6_if_up (ifp=0xc32f4800)
at /usr/src/sys/netinet6/in6.c:2326
#27 0xc025b827 in if_route (ifp=0xc32f4800, flag=1, fam=0)
at /usr/src/sys/net/if.c:1120
#28 0xc025b881 in if_up (ifp=0x0) at /usr/src/sys/net/if.c:1147
#29 0xc04a0a74 in ?? ()
#30 0xc04a0b20 in ?? ()
#31 0xc04a0e51 in ?? ()
#32 0xc01fe92b in sysctl_root (oidp=0x0, arg1=0xd2c09ca8, arg2=-1020035060,
req=0xc32f4800) at /usr/src/sys/kern/kern_sysctl.c:1150
#33 0xc01febad in userland_sysctl (td=0x0, name=0xd2c09ca8, namelen=4,
old=0xc333800c, oldlenp=0xc32f4800, inkernel=0, new=0xd2c09ca8,
newlen=0,
retval=0xd2c09ca4) at /usr/src/sys/kern/kern_sysctl.c:1254
#34 0xc01fe9f0 in __sysctl (td=0x0, uap=0xd2c09d10)
at /usr/src/sys/kern/kern_sysctl.c:1184
#35 0xc03148ce in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 4, tf_esi = 0,
tf_ebp = -1077939032, tf_isp = -759128716, tf_ebx = 0, tf_edx =
-1077936551, tf_ecx = -1077936880, tf_eax = 202, tf_trapno = 12, tf_err
= 2, tf_eip = 134587879, tf_cs = 31, tf_eflags = 663, tf_esp =
-1077939076, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1033
#36 0xc0304a1d in Xint0x80_syscall () at {standard input}:140
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
rc.conf ifconfig lines fail
Ever since RC2 I have had to manually execute the following two lines from my rc.conf, because they are not set at boot. ifconfig_fxp0="DHCP" ifconfig_wi0="inet up ssid my_ap mediaopt hostap" Have I missed something? Thanks, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI Error on FreeBSD-CURRENT
ACPI-1287: *** Error: Method execution failed, E_AML_UNINITIALIZED_LOCAL can't fetch resources for \\_SB_.PCI0.FDC0 - AE_AML_UNINITIALIZED_LOCAL I have a Tyan S1834 and see the above error during boot. I'm not sure if this is such a big problem but it would be nice to eliminate the error. Thanks, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI Error on FreeBSD-CURRENT
Nate Lawson wrote: > On Thu, 16 Jan 2003, Peter Schultz wrote: > > >ACPI-1287: *** Error: Method execution failed, E_AML_UNINITIALIZED_LOCAL > >can't fetch resources for \\_SB_.PCI0.FDC0 - AE_AML_UNINITIALIZED_LOCAL > > > >I have a Tyan S1834 and see the above error during boot. I'm not > >sure if this is such a big problem but it would be nice to eliminate > >the error. > > > It means there's a syntax error in your asl (in particular, a > reference of a variable without declaration). You could go through > the iasl dance to fix it or just disable acpi (see INSTALL.TXT for how > to do this). > > It looks like you won't be able to use your floppy drive until you use > a workaround. Luckily my floppy drive works regardless of the error message. That's why I wonder about what exactly the error message is saying. I'm not sure if it's absolutely harmless, or if it's hinting at some bigger problem. One thing to note is that I'm not able to use my USB mouse when I'm using an SMP kernel. I've noticed that Josef Karthauser is working on busdma for USB. Hopefully this will correct my USB SMP issue. With SMP I also have a hang. A shutdown or restart will get stuck waiting for vnlru to stop, or sometimes it will get down to the ACPI prompt. If I hit the power button at that point it will continue. Is this possibly some kind of ACPI SMP timing issue? Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bad ACPL asl's on motherboards
John Baldwin wrote: On 16-Jan-2003 Terry Lambert wrote: >"Joel M. Baldwin" wrote: > >>I gather that there are quite a few Motherboards with bad ACPI asl's >>on them. I know that my Abit BP6 sure has problems. As a result I >>can't run ACPI. >> >>What are those of us with these motherboards supposed to to? >> >>I realize that we can use acpidump to get the asl, correct it, >>and then recompile it using iasl from the acpicatools port, to >>generate the aml that can be used during boot. > >There are several things you can do, one of which is what you >have suggested, though you do not go far enough: > >1)Correct the ASL, make a file modification so that > FreeBSD can run on the system with the incorrect > ASL, and then *notify the motherboard and BIOS > vendors of the correction, and the reason for it*. > >2)The ASL works *fine* with the Windows ACPI code; > *correct* the FreeBSD code so that it *also* works > fine for FreeBSD (i.e. if the FreeBSD code were a > line-for-line duplicate of the Windows code, then > FreeBSD would not be having these problems, where > Windows does not, would it...). Well, the problem here is that we don't write this code, Intel does. The problem is that Mike Smith quit. If I remember correctly, he fixed two of these for me when he was working on CURRENT. Googling `Mike Smith freebsd acpi' gets 482 results. If someone can get close to him, this stuff might get solved. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
i386 SCHED_ULE buildkernel error
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/kern/sched_ule.c cc1: warnings being treated as errors /usr/src/sys/kern/sched_ule.c: In function `sched_check_runqs': /usr/src/sys/kern/sched_ule.c:624: warning: implicit declaration of function `runq_depth' *** Error code 1 Stop in /usr/obj/usr/src/sys/MAXKERNEL. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. With -Wno-error: linking kernel sched_ule.o: In function `sched_check_runqs': sched_ule.o(.text+0x99f): undefined reference to `runq_depth' sched_ule.o(.text+0x9af): undefined reference to `runq_depth' sched_ule.o(.text+0x9c8): undefined reference to `runq_depth' sched_ule.o(.text+0x9d8): undefined reference to `runq_depth' *** Error code 1 Stop in /usr/obj/usr/src/sys/MAXKERNEL. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ULE Update
Jeff Roberson wrote: I have reproduced the lagging mouse issue on my laptop. I tried moused to no effect. Eventually, I grudgingly installed kde and immediately started encountering problems with mouse lag. It would seem that twm was not stressing my machine in the same ways that kde is. ;-) I have a Tyan S1832DL with dual PII 350s, 384 MB of ram, Adaptec 2940 scsi controler w/Seagate ST39102LW disk, and a voodoo 3 3000. I've been running ULE for a while now and have noticed that I don't have to be in X to see the scheduling problem, I don't even have to be in multi-user mode to notice. Typing and executing commands in single user mode I can see the scheduling is not fluid. For instance, I can type in and execute the sync command so fast that I'm finished before the characters actually get printed and the prompt returns. I don't think it's ever been more than a one second delay, but sometimes it's been close. I suspect a problem with IPC. I will know more soon. There have also been a few reports of problems related to nice. I was able to reproduce some awkward behavior but I have nothing conclusive yet. There is still a known issue with hyperthreading. I'm waiting on some of john baldwin's work to fix this. If you halt logical cpus your machine will hang. Expect some resolution on the ULE problems within a week or so. Thanks for the detailed bug reports everyone. Your dedication to FreeBSD is outstanding, I always look forward to seeing your name in the cvs reports. Thanks for your efforts, Jeff. Cheers, Jeff Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: hiding e-mail adresses needed badly
At this point in time it's downright irresponsible not to hide our addresses. I've been lurking on this list about a month to get caught up with -current issues. Friday was both the first mail I sent to the list, and the first use of this e-mail address. The only incoming mail was from the FreeBSD lists I subscribed to. However, since that fateful e-mail I have been viciously attacked by spammers posing as Microsoft security updaters. These spams include attachments making them all around 150KB in size. Maybe others of you have seen them? As far as I can tell, these guys are targeting the FreeBSD lists, exploiting them terribly! This list's charter states that spam will be blocked. Please enforce the list charter, with prejudice. It would be best if subscribers could just choose to have their address published or not. I can understand being so dedicated to the cause that you're willing to take on some spam. Non-subscribers addresses should definitely not be published. Sincerely, Pete... Wilko Bulte wrote: On Wed, Oct 15, 2003 at 03:29:21PM +0400, Andrey Chernov wrote: I fail to see why this is relevant to -current but OK.. I think that the opportunity to do this has long since passed. Just type your name in Google and see what happens.. Wilko Due to increased activity of SPAM harvesters what are our plans to hide our addresses from public WWW? I mean all browseable mailing lists, FreeBSD site, CVS via WWW, PRs, ports and docs. As I think, simple form will be enough to stop them. -- Andrey Chernov | http://ache.pp.ru/ ---end of quoted text--- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UFS file system problem in either stable or current
Dan Strick wrote: There seems to be an inconsistency between release 4.9-RC and 5.1 ufs support. If I fsck the same ufs (type 1 of course) file system on both releases, each claims that the other has left incorrect summary data in the superblock. Presumably only one can be correct. I just don't know which to blame. I couldn't find a FreeBSD problem report about bad summary data. I will submit one, but since FreeBSD 4.9 is about to be released, someone might like to check this out. I happen to have multiple FreeBSD operating systems installed on the same computer. This might also be an issue if you move an external disk between computers. I don't know if the problem shows up on all file systems. It seems to happen on all the half dozen or so of the file systems that my 4.9-RCx and 5.1 systems share. There is no problem AFAIK, you just have to fsck with the matching executable. A lot has changed with FreeBSD 5, spend some time with the -current archive and you will learn more. I'm sure you noticed how your findings are consistently inconsistent. Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SCSI error using gnome-cd
This is an actual SCSI drive so there's no ATAng or atapicam issue here.
Here's the output I see from gnome-cd:
** (gnome-cd:822): WARNING **: Error getting leadout
** (gnome-cd:822): WARNING **: Error getting leadout
(gnome-cd:822): CDDBSlave2-CRITICAL **: file cddb-slave-client.c: line
197 (cddb_slave_client_query): assertion `nsecs > 0' failed
slave-mike wrote:
if you can, add -force or equivilent to the command line.
there seem to be problems with ATAng and atapicam. :(
Peter Schultz wrote:
I have set the permissions to properly read the CD, and I can play audio
CDs using xmms, but when I try using gnome-cd I get the following:
(cd0:ahc0:0:4:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 2 0 0 0 0 c
0 c 0
(cd0:ahc0:0:4:0): CAM Status: SCSI Status Error
(cd0:ahc0:0:4:0): SCSI Status: Check Condition
(cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0
(cd0:ahc0:0:4:0): Invalid field in CDB
(cd0:ahc0:0:4:0): Unretryable error
(cd0:ahc0:0:4:0): READ SUB-CHANNEL. CDB: 42 2 40 1 0 0 1c 0 18 0
(cd0:ahc0:0:4:0): CAM Status: SCSI Status Error
(cd0:ahc0:0:4:0): SCSI Status: Check Condition
(cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0
(cd0:ahc0:0:4:0): Invalid field in CDB
(cd0:ahc0:0:4:0): Unretryable error
(cd0:ahc0:0:4:0): READ SUB-CHANNEL. CDB: 42 2 40 1 0 0 1b 0 18 0
(cd0:ahc0:0:4:0): CAM Status: SCSI Status Error
(cd0:ahc0:0:4:0): SCSI Status: Check Condition
(cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0
(cd0:ahc0:0:4:0): Invalid field in CDB
(cd0:ahc0:0:4:0): Unretryable error
(cd0:ahc0:0:4:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 2 0 0 0 0 c
0 c 0
(cd0:ahc0:0:4:0): CAM Status: SCSI Status Error
(cd0:ahc0:0:4:0): SCSI Status: Check Condition
(cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0
(cd0:ahc0:0:4:0): Invalid field in CDB
(cd0:ahc0:0:4:0): Unretryable error
(cd0:ahc0:0:4:0): READ SUB-CHANNEL. CDB: 42 2 40 1 0 0 1c 0 18 0
(cd0:ahc0:0:4:0): CAM Status: SCSI Status Error
(cd0:ahc0:0:4:0): SCSI Status: Check Condition
(cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0
(cd0:ahc0:0:4:0): Invalid field in CDB
(cd0:ahc0:0:4:0): Unretryable error
Here's some info about my device:
GEOM: create disk cd0 dp=0xc36a0e00
cd0 at ahc0 bus 0 target 4 lun 0
cd0: Removable CD-ROM SCSI-2 device
cd0: 10.000MB/s transfers (10.000MHz, offset 8)
Pete...
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
LOR During OpenOffice Build
This has the elements of a false positive, but here it is anyway: lock order reversal 1st 0xc3bcfde0 vm object (vm object) @ /usr/src/sys/vm/swap_pager.c:1323 2nd 0xc06f60a0 swap_pager swhash (swap_pager swhash) @ /usr/src/sys/vm/swap_pager.c:1838 3rd 0xc1036b90 vm object (vm object) @ /usr/src/sys/vm/uma_core.c:876 Stack backtrace: backtrace(c0668b52,c1036b90,c067678e,c067678e,c067763c) at backtrace+0x17 witness_lock(c1036b90,8,c067763c,36c,1) at witness_lock+0x672 _mtx_lock_flags(c1036b90,0,c067763c,36c,1) at _mtx_lock_flags+0xba obj_alloc(c10207e0,1000,d38859df,101,c06ca450) at obj_alloc+0x3f slab_zalloc(c10207e0,1,c067763c,68c,c10207f4) at slab_zalloc+0xb3 uma_zone_slab(c10207e0,1,c067763c,68c,c1020890) at uma_zone_slab+0xd6 uma_zalloc_internal(c10207e0,0,1,5c1,72e,c06cb8c8) at uma_zalloc_internal+0x3e uma_zalloc_arg(c10207e0,0,1,72e,2) at uma_zalloc_arg+0x3b9 swp_pager_meta_build(c3bcfde0,9,0,2,0) at swp_pager_meta_build+0x194 swap_pager_putpages(c3bcfde0,d3885bd0,7,0,d3885b20) at swap_pager_putpages+0x32d default_pager_putpages(c3bcfde0,d3885bd0,7,0,d3885b20) at default_pager_putpages+0x2e vm_pageout_flush(d3885bd0,7,0,eb,c071f820) at vm_pageout_flush+0x17a vm_pageout_clean(c153bd90,0,c0677457,32a,0) at vm_pageout_clean+0x305 vm_pageout_scan(0,0,c0677457,5a9,1f4) at vm_pageout_scan+0x669 vm_pageout(0,d3885d48,c06633e1,311,0) at vm_pageout+0x31b fork_exit(c05ecee0,0,d3885d48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd3885d7c, ebp = 0 --- Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: floppies
No problem with formatting or writing floppies here under heavy system load and even though this message--fdc0: cmd 3 failed at out byte 1 of 3--has been output twice at boot for probably over a year. The floppies I used even came from a dusty pile of old driver disks. :-) Pete... Dag-Erling Smørgrav wrote: anyone else having trouble with floppies? I tried a bunch of different disks in two different machines (5.1-CURRENT with brand new drive, 4.9-PRERELEASE with an older but presumed-good drive) and all I get are I/O errors; fdformat sometimes works and sometimes doesn't, and any attempt to actually read or write data fails. # uname -a FreeBSD ada.des.no 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #5: Fri Sep 5 22:56:22 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/ada i386 # fdformat fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing fdformat: ioctl(FD_FORM): Input/output error # dd if=/dev/zero of=/dev/fd0c dd: /dev/fd0c: Input/output error 1+0 records in 0+0 records out 0 bytes transferred in 2.634334 secs (0 bytes/sec) and the console shows: fd0: recal failed ST0 70 cyl 0 last message repeated 2 times fd0: recal failed ST0 78 cyl 0 fd0c: hard error writing fsbn 0 (No status) on -CURRENT: # fdformat fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing VEVV done. Errors encountered: Cyl Head Sect Error 661 12 wrong cylinder (format mismatch) (although a previous run succeeded) I'm having a hard time believing this is a hardware problem, although there might conceivably be an environmental factor which affects both systems since they are in the same room. DES ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
new interrupts not working for me
I have a Tyan S1832DL w/dual pii 350s and it's not able to boot. Seems to be having trouble with my adaptec scsi controller, I get a whole bunch of output like this hand transcribed bit, it comes after "waiting 15 seconds for scsi devices to settle": ahc0 timeout SCB already complete interrupts may not be functioning Infinite interrupt loop INTSTAT=0(probe3:ahc0:0:3:0): SCB 0x6 - timed out Anyone else seeing this? There are probably 100+ related lines of output, I'll have to configure serial debugging if you need to see it. Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: new interrupts not working for me
John Baldwin wrote: On 05-Nov-2003 Peter Schultz wrote: I have a Tyan S1832DL w/dual pii 350s and it's not able to boot. Seems to be having trouble with my adaptec scsi controller, I get a whole bunch of output like this hand transcribed bit, it comes after "waiting 15 seconds for scsi devices to settle": ahc0 timeout SCB already complete interrupts may not be functioning Infinite interrupt loop INTSTAT=0(probe3:ahc0:0:3:0): SCB 0x6 - timed out Anyone else seeing this? There are probably 100+ related lines of output, I'll have to configure serial debugging if you need to see it. The dmesg output excluding all the ahc0 errors would help figure out why your interrupts aren't working. However, I just committed a patch that might fix your problem. Now the kernel just dies and the machine reboots right in the beginning when it's setting up the ACPI/APIC stuff. Of course, with ACPI off, there's no apparent problem with the kernel. Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: new interrupts not working for me
John Baldwin wrote: On 06-Nov-2003 Peter Schultz wrote: John Baldwin wrote: On 05-Nov-2003 Peter Schultz wrote: I have a Tyan S1832DL w/dual pii 350s and it's not able to boot. Seems to be having trouble with my adaptec scsi controller, I get a whole bunch of output like this hand transcribed bit, it comes after "waiting 15 seconds for scsi devices to settle": ahc0 timeout SCB already complete interrupts may not be functioning Infinite interrupt loop INTSTAT=0(probe3:ahc0:0:3:0): SCB 0x6 - timed out Anyone else seeing this? There are probably 100+ related lines of output, I'll have to configure serial debugging if you need to see it. The dmesg output excluding all the ahc0 errors would help figure out why your interrupts aren't working. However, I just committed a patch that might fix your problem. Now the kernel just dies and the machine reboots right in the beginning when it's setting up the ACPI/APIC stuff. Of course, with ACPI off, there's no apparent problem with the kernel. Ok. Did the old kernel break before with ACPI turned off? It should have. By the way, I've committed a fix for the ACPI breakage. The "new interrupt" kernels I've built have worked fine with ACPI off. The immediate crash is fixed, but now I'm back to the trouble with my SCSI controller. I'll try to get the output from that to you. Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
floppy install troubles
I'm having trouble installing with the 5.1-CURRENT-20031110-JPSNAP floppies I got off snapshots.jp.freebsd.org. First off, I tried to create a new slice and it wants to use /dev/ad0p1. I don't believe the p is correct. I tried again without changing the slices at all, and when newfs ran the install stopped with this error: "newfs: Cannot retrieve operator gid". Thanks, Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: floppy install troubles
David O'Brien wrote: On Thu, Nov 13, 2003 at 08:10:34PM +0900, Jun Kuriyama wrote: At Wed, 12 Nov 2003 03:48:01 + (UTC), Peter Schultz wrote: I'm having trouble installing with the 5.1-CURRENT-20031110-JPSNAP floppies I got off snapshots.jp.freebsd.org. First off, I tried to create a new slice and it wants to use /dev/ad0p1. I don't believe the p is correct. I tried again without changing the slices at all, and when newfs ran the install stopped with this error: "newfs: Cannot retrieve operator gid". I saw "p" slice too. Is your disk is fresh one (no write after buying), or already used one? Mine was totally fresh. I had just created a HW RAID 0+1 setup. > Mine is totally old and suffers from the same exact problems with today's JPSNAP. I was thinking the p problem would be fixed with src/lib/libdisk/create_chunk.c 1.83. Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
making a release
I'm trying to build a set of release floppies, but my setting for CHROOTDIR seems to be ignored and the release gets dumped in my root file system under /R. Shouldn't /R be installed under whatever I set CHROOTDIR to? Thanks, Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: making a release
Scott Long wrote: I use the following all of the time: cd /usr/src/release ; make release BUILDNAME=5.1-CURRENT CHROOTDIR=/usr/release CVSROOT=/usr/ncvs I have NODOC=YES NOPORTS=YES and thought I'd be able to get by with EXTSRCDIR=/usr/src in place of CVSROOT=/usr/ncvs. Looks like EXTCRCDIR is not widely used, but would be convenient for a local user. Pete... Scott On Thu, 13 Nov 2003, Peter Schultz wrote: I'm trying to build a set of release floppies, but my setting for CHROOTDIR seems to be ignored and the release gets dumped in my root file system under /R. Shouldn't /R be installed under whatever I set CHROOTDIR to? Thanks, Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: signal 12's everywhere on Current with update this morning.
Richard Coleman wrote: Andy Farkas wrote: Richard Coleman wrote: 1. make buildworld 2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE 3. make installkernel KERNCONF=NAME_OF_KERNEL_FILE 4. shutdown -r now 5. boot into single user mode 6. fsck -p 7. mount -u / 8. mount -a -t ufs 9. swapon -a 9.5 adjkerntz -i Yep, forgot that part. I keep all my system clocks on UTC so I never do this step when building world. Running -CURRENT, I've gotten into the pattern of always building and installing a new /usr/include, just to be extra safe. 10a. cd /usr; mv include inc.old; mkdir include; cd /usr/src; make includes 10. make installworld 11. mergemaster 12. reboot Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem booting JPSNAP kernel
Matt Haught wrote: I have been trying to get the latest current iso to install > I have also had negative results with the floppies from the 16th, but the error for me is that no kernel modules want to get loaded, ergo no networking. Good news: It looks like the problems I had creating filesystems using sysinstall have been corrected. Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
floppy install [was: cvs commit: src/release/i386 drivers.conf]
Jun Kuriyama wrote: kuriyama2003/11/12 00:08:16 PST FreeBSD src repository Modified files: release/i386 drivers.conf Log: Move cd9660 module from 3rd floppy to 2nd to unbreak release. Revision ChangesPath 1.31 +1 -1 src/release/i386/drivers.conf > It looks like the build has broken again in the same place: ftp://snapshots.jp.freebsd.org/pub/FreeBSD/snapshots/i386/5.1-CURRENT-20031118-JPSNAP.log If the beta is coming out tomorrow, it would be cool to have this fixed. The floppies from the 16th cannot load any of the kernel modules, I think the relevant error message is: link_elf: symbol _mtx_assert undefined Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] Please test SMP changes
John Baldwin wrote: [ Bcc'd to various arch mailing lists ] Please test the patch at http://www.FreeBSD.org/~jhb/patches/smp.patch You can apply it to a sys/ check out by using patch -p6. It moves the setting of mp_maxid into a separate function (cpu_mp_setmaxid()) that is called before loader tunables so that UMA and others can use it. cpu_mp_probe() is now called at SI_SUB_CPU / SI_ORDER_SECOND like it used to be. This is necessay to re-enable the ACPI module on i386. I have tested it on i386 but not on other archs. Please be sure to test that a normal SMP kernel works as well as booting an SMP kernel with 'kern.smp.disabled'. cpu_mp_probe() is no longer called if SMP is disabled in the loader using the tunable. Thanks. What all do I need to adjust on my end, other patches? I took 'device acpi' out of my kernel, but if I try to boot with the acpi module loaded, the kernel still uses MPTable for interrupts: Copyright (c) 1992-2003 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.1-CURRENT #0: Wed Nov 19 08:55:07 CST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MAXKERNEL_DEBUG Preloaded elf kernel "/boot/kernel/kernel" at 0xc07d8000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc07d8250. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (350.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbff real memory = 402587648 (383 MB) avail memory = 385548288 (367 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0168: *** Error: Could not transition to ACPI mode. acpi0: Could not enable ACPI: AE_NO_HARDWARE_RESPONSE device_probe_and_attach: acpi0 attach returned 6 Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Where is compat4x v 5.0CURRENT-20030218?
CARTER Anthony wrote: Hey, I am looking for 5.0-CURRENT-20030218 version of compat4x for running ymessenger, but I can only find 20020917 version on 4 different FTP mirrors (including freebsd's main one). Any ideas? Where is this? Also, the 200212xx directory for compat4x is empty...Normal? Anthony Carter why not use make.conf: COMPAT4X= yes After all, you are using CURRENT. ???, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Need ALSA [was: Re: MIDI on SB Live! ?]
[EMAIL PROTECTED] wrote: Hello, just out of curiosity: Is someone working in MIDI support for Creative EMU10K1 based sound cards (aka Soundblaster Live!) ? Regards, Julian Stecklina Having a port of ALSA would sure round out 5.2 nicely, and would get you MIDI support: http://www.alsa-project.org/ This can easily happen if we get behind a developer. ALSA has been sponsored by SuSE for the benefit of Linux, and there's no reason we can't pull together our resources to do the same for our OS. I'm sure someone will step forward to do the port if we have the cash for them to comfortably sit in front of their computer until the port is complete. I'd certainly be more than willing to throw some money into a paypal account or whatever, and I think there are others who would too. OSS is so 20th century, lets get FreeBSD into 21st century sound architecture design. :-) If you're a developer seriously interested in this, lets talk. So much of FreeBSD development is sponsored by Universities and whatnot that we take it for granted. When stuff like ALSA doesn't get ported right away, I feel we need to realize our responsibility to contribute to the project as well. Sincerely, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Need ALSA [was: Re: MIDI on SB Live! ?]
Michael Nottebrock wrote: On Saturday 22 March 2003 14:52, Peter Schultz wrote: [EMAIL PROTECTED] wrote: Hello, just out of curiosity: Is someone working in MIDI support for Creative EMU10K1 based sound cards (aka Soundblaster Live!) ? Regards, Julian Stecklina Having a port of ALSA would sure round out 5.2 nicely, and would get you MIDI support: http://www.alsa-project.org/ I think you wouldn't really do anyone a favour, including the ALSA folks, if you went and made a port right now. The ALSA project is still not at 1.00 status and still quite in-flux. One could go either way with this. Leave it for after 1.0, or grab it now and help build it up for a better 2.0. Or I guess we could initiate the ABSDSA and have support for both ALSA and OSS. Wouldn't this be even more work though? This can easily happen if we get behind a developer. ALSA has been sponsored by SuSE for the benefit of Linux, and there's no reason we can't pull together our resources to do the same for our OS. I'm sure someone will step forward to do the port if we have the cash for them to comfortably sit in front of their computer until the port is complete. I'd appreciate sponsoring somebody to work on our existing newpcm stuff and add the missing bits and pieces much more. Donating hardware (soundcards and MIDI-devices) would probably help very much already. OSS is on the outs. New applications that are ALSA only will soon be common, won't they? Newpcm is what, five years old? Whatever it is, it ain't new anymore. Of course, maybe I'm completely mistaken about the whole situation and all newpcm needs is a boost. What is the right answer? Does OS X have a completely proprietary sound arch? It would be nice to be able to work with what they've got too. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Need ALSA
Dag-Erling Smørgrav wrote: Peter Schultz <[EMAIL PROTECTED]> writes: Having a port of ALSA would sure round out 5.2 nicely, and would get you MIDI support: http://www.alsa-project.org/ This can easily happen if we get behind a developer. Not so. ALSA is poorly designed (there is no hardware abstraction layer below the driver layer) and would represent a significant challenge to port, not to mention maintain once ported. DES I didn't mean to imply that it would be trivial or that it would be complete after the initial port, but I still hold fast that it's easily possible. There's certainly no lack in talent around here, it's just a matter of the group's will to get it done. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Removing Sendmail
Hi, I hope that core will approve removing sendmail from FreeBSD-CURRENT. Thank you, Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing Sendmail
Terry Lambert wrote: Peter Schultz wrote: Hi, I hope that core will approve removing sendmail from FreeBSD-CURRENT. I'm pretty sure they will, just as soon as someone provides patches to make installed base system components like sendmail into "preinstalled packages", and then steps up and makes some other MTA and MSA able to be installed by default instead, so that things like "/etc/daily", "/etc/weekly", and so on can still send an email to the local "root" user upon completion. Why not just have these logged by default instead? Like /var/log/daily, and whatnot. Anyone with half a care about this stuff can easily make their own modifications, those who don't care will never know the difference. On a simple installation where the user is careless, these e-mails are spamming roots mailbox. Imagine the hundreds if not thousands of ignored messages. PS: This comes up every time a sendmail CERT advisory happens, but then no one provides the necessary patches to make email continue to work with sendmail deinstalled, or the package files to allow it to be deinstalled and replaces easily. I'm sorry for beating a dead horse. A guy and I from tcbug were just trying to fix his postfix installation, he does not know what happened, it just stopped working. There would not have been a problem if sendmail wasn't tied into the system so closely. I'm just hoping core will say, "submit a working solution and it will be done," so that there's a little inspiration here. Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MIDI
David Schultz wrote: Thus spake Thanjee Neefam <[EMAIL PROTECTED]>: I was very happy when compiling my 5.0 kernel. For the first time "device midi" compiled without giving any errors. This abnormal excitement only led to misery when I discovered after rebooting that there still was no MIDI. Is MIDI going to be implemented soon? Who is working on it? Can I help them? (I am not a very good programmer, but I can hack pre existing code, and I am good at testing). MIDI is the ONLY thing stopping me from running FreeBSD exclusively. FYI, the non-free OSS driver supports MIDI: http://www.opensound.com/bsd.html Apparently even this is not complete, however: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1250661+0+archive/2003/freebsd-current/20030323.freebsd-current One interesting thing to note from that thread, is that Yuriy Tsibizov is into the development of this stuff, but does not have all the equipment needed to conduct testing. I don't know what hardware you have, but this is what he's been working on: http://chibis.persons.gfk.ru/audigy/ Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing Sendmail
Terry Lambert wrote: If you look over the historical cases of this discussion, you'll see that the answer always comes down to "make the system more modular, so people can replace XXX with YYY and quit bothering us; please send patches". 8-) 8-). Thanks for your help on this. I've been getting so many search results that I've been unable to determine the exact problem myself. So, one absolute requirement is that the system have both an mta, and an msa. When you say msa, does this include pop&imap capabilities? Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing Sendmail
John Baldwin wrote: On 02-Apr-2003 Peter Schultz wrote: I'm sorry for beating a dead horse. A guy and I from tcbug were just trying to fix his postfix installation, he does not know what happened, it just stopped working. There would not have been a problem if sendmail wasn't tied into the system so closely. I'm just hoping core will say, "submit a working solution and it will be done," so that there's a little inspiration here. Pete... First, core@ is not the appropriate body for that type of request. > Both current@ and arch@ are much better targets. I understand, thanks for clarifying. Second, is NO_SENDMAIL + the postfix port inadequate? I guess. I was helping him on #tcbug this morning, and he certainly missed something somewhere between the two. He claimed it "just stopped working." I don't know what all he did, but he was sure going crazy trying to fix it. I helped him get around the problem, but I couldn't help but think it would be nice for FreeBSD administrators to have a smoother solution. How about requiring a decision at install time, during the final configuration: [x] sendmail ... (default) [ ] postfix ... [ ] exim ... [ ] qmail ... [ ] none (caution: desktop users only, insecure use of syslog) Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing Sendmail
On Wed, Apr 02, 2003 at 10:27:04AM -0700, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Peter Schultz writes: > : I hope that core will approve removing sendmail from FreeBSD-CURRENT. > > Request denied. > > 1) you made no case for it: Everybdoy knows this is a contentious >issue, yet no reasons were given. > 2) You cc'd core and a public mailing list. Don't ever do that again. Duly noted. > 3) Get consensus on arch@ first. If you can't, then chances are good >that there won't be support for this. Be sure to include how basic >systems will do email, and be prepared to supply patches to the >install system. > I'll try one list at a time then. 1) Coordination between gshapiro@, as the apparent src tree maintainer, and dinoex@, as with the port, to prepare sendmail for it's switch. 2) Find out how NetBSD is solving not having a mailer. Anyone here know, or have a friend that can help? 3) Notify relevant ports maintainers of the impending change. 4) Discuss where to present this during installation, implement. I know that I cannot fix this problem by myself, so I kindly ask for your assistance. I do not endorse the "parting out" of FreeBSD either, only to remove it's dependance on sendmail. I think we can all see how this is related to perl, where a lot of people are going to have it one way or the other, they might as well have it with the flexibilty and ease-of-use from using ports. Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ports problem after new world
After updating 5.1-CURRENT this morning I get the following error when trying to build any port: Your system is too old to use this bsd.port.mk. You need a fresh make world or an upgrade kit. Please go to http://www.FreeBSD.org/ports/ or a mirror site and follow the instructions. I always do my best to follow the handbook upgrade path, so I'm not sure if I've done something wrong or if there's a problem with a commit that was made within the last 24hrs. Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld problems with today's sources
On Mon, 2002-07-01 at 09:02, Luigi Rizzo wrote: > On Mon, Jul 01, 2002 at 09:58:04AM -0400, Andrew Gallatin wrote: > ... > > That's actually rather scary. It implies that a freshly checked out > > tree checked out with plain 'cvs co src' is no longer buildable. > > c'mon... it is not that terrible, just a matter of adding a -P flag > Do these problems concern someone using cvsup? I've been having a terrible time with -current lately. Of course I realize development is going full speed, I'm being patient and using the down time to encourage others to turn to FreeBSD. The file system is blazing fast and as soon as the kernel smooths out FreeBSD-5.0 is going to rock. I'm very happy with FreeBSD. It does take a very great deal of studying, but once you've done that it's so ultimately powerful. To my dismay I've only just scratched the surface, but I'm not giving up yet! My thanks goes out to all those valuable FreeBSD commits. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: I think X is making this whole thing unstable..
On Thu, 2002-07-25 at 16:30, Alex Zepeda wrote: > I can buildworld no problem, play mp3s, read mail. But as soon as I play > around in X... boom the system falls over. > As of this morning's new world I cannot open galeon/mozilla without a complete lockup. I've also been locking up the system under X when disk i/o gets heavy. That may be why galeon/mozilla won't run because I'll hear the disk loading the program and right at the peak of it the system freezes. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
portupgrade problem
Since yesterday I've been getting the following error when running the command `portsclean -DDi': Detecting unreferenced distfiles... (eval):9:in `chdir': No such file or directory - "\"/usr/ports/Mk/bsd.port.mk\", line 1621: warning: duplicate script for target \".BEGIN\" ignored\n\"/usr/ports/Mk/bsd.port.mk\", line 1622: warning: duplicate script for target \".BEGIN\" ignored\n/usr/ports/distfiles" (Errno::ENOENT) from (eval):9:in `chdir' from /usr/local/sbin/portsclean:555:in `scan_distfiles' from /usr/local/sbin/portsclean:213:in `distclean' from /usr/local/sbin/portsclean:140:in `main' from /usr/local/sbin/portsclean:66:in `initialize' from /usr/local/sbin/portsclean:66:in `new' from /usr/local/sbin/portsclean:66:in `main' from /usr/local/sbin/portsclean:672 I don't run the command very often, so I'm not sure when it broke. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Firewire support
On Thu, 2002-08-08 at 16:45, Terry Lambert wrote: > Julian Elischer wrote: > > On Thu, 8 Aug 2002, Katsushi Kobayashi wrote: > > > Did you suggest the same API should be used on both Darwin and FreeBSD ? > > > Or, should we share the same code on the device driver level ? > > > > > > Although I have not read the terms and condition carefully, I am afraid > > > if once > > > read the source code, I cannot write any firewire kernel code. > > > > There is no problem with that.. > > The courts have said that what you know in your head can not be > > withheld from your use. > > You may not be able to DIRECTLY COPY it but you can use it as a source > > of information. > > (depending on the coppyright you may even be able to copy it of course :-) > > He is in Japan. > > Japan is one of the few places, besides the U.S., which permits > software patents. In additioan, they have a number of draconian > laws about reverse engineering, and so on, similar to the laws > that have been recently passed or are in the process of being > passed in the U.S.. You can not sell or rent a game cartridge > for a console game there, for example. > > He may need someone else to agree to the license for him, and > then document the API without coping the information directly. > I'm not sure why Apple would bite the hand that feeds it. BSD is not powerless against them, I see no reason to be afraid. My argument is that Apple has made claims that they will be contributing back to BSD. So, if Katsushi can't go check out their code and make FreeBSD's compatible, then they will be going against their word, and that will not look good to very many of us. Apple is in plenty of hot water already, they don't need a bunch of pissed off BSD users too. In light of the recent and long overdue questioning of business ethics, I think it's our duty to challenge Apple. Apple could have taken the code and walked away, but since they want to be a part of the process they're going to have to deal with us. Of course, it's not my neck on the line, so I totally respect Katsushi's hesitance. If the decision is made to go ahead and Apple follows up with legal action, I can guarantee you that the very next day I will be on the phone with as many senators as I can. Not only that but I would not stop until all parties names are clear and they are free to go ahead with writing the code. I don't think my opinion is out of line, and I have confidence that many of you support this attitude. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
dmesg warnings, related to acpi?
I have two \\_SB_.PCI0 related warnings being output at boot. The one about AE_BAD_DATA is fairly recent, but I don't know what kernel it appeared with. I moved recently and haven't have a smooth upgrade path. The FDC0 - AE_AML_UNINITIALIZED_LOCAL warning has been around for some time. Copyright (c) 1992-2002 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.0-CURRENT #0: Tue Oct 22 09:07:41 CDT 2002 root@max:/usr/obj/usr/src/sys/MAXKERNEL Preloaded elf kernel "/boot/kernel/kernel" at 0xc053d000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc053d0a8. Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (933.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbff real memory = 402587648 (393152K bytes) avail memory = 384352256 (375344K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 9 IOAPIC #0 intpin 17 -> irq 10 IOAPIC #0 intpin 18 -> irq 5 IOAPIC #0 intpin 19 -> irq 11 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard Using $PIR table, 8 entries at 0xc00fdb50 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz can't fetch resources for \\_SB_.PCI0.FDC0 - AE_AML_UNINITIALIZED_LOCAL acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xc f8-0xcff on acpi0 pcib0: could not get PCI interrupt routing table for \\_SB_.PCI0 - AE_BAD_DATA initial configuration before setting priority for links before fixup boot-disabled links - after fixup boot-disabled links -- arbitrated configuration - pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: <3dfx Voodoo5> port 0xc000-0xc0ff mem 0xd000-0xd7ff,0xd800-0xd bff irq 9 at device 0.0 on pci1 info: [drm] Initialized tdfx 1.0.0 20010216 on minor 0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 11 at device 7.2 on pc i0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 pci0: at device 7.3 (no driver attached) ahc0: port 0xd800-0xd8ff mem 0xe5101000 -0xe5101fff irq 11 at device 15.0 on pci0 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs fxp0: port 0xdc00-0xdc1f mem 0xe500-0xe50f ,0xe510-0xe5100fff irq 10 at device 17.0 on pci0 fxp0: Ethernet address 00:a0:c9:10:bc:94 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto wi0: mem 0xe5102000-0xe5102fff irq 5 at device 18.0 on pci0 wi0: 802.11 address: 00:05:5d:ee:ec:90 wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary 1.00.05, Station 1.03.04 pcm0: port 0xe000-0xe01f irq 9 at device 20.0 on pci0 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0" locked from /usr/src/sy s/dev/sound/pcm/sound.c:134 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0" locked from /usr/src/sy s/dev/sound/pcm/sound.c:134 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0" locked from /usr/src/sy s/dev/sound/pcm/sound.c:134 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0:fake" locked from /usr/s rc/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0" locked from /usr/src/sy s/dev/sound/pcm/sound.c:134 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0:fake" locked from /usr/s rc/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0" locked from /usr/src/sy s/dev/sound/pcm/sound.c:134 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0:fake" locked from /usr/s rc/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0" locked from /usr/src/sy s/dev/sound/pcm/sound.c:134 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0:fake" locked from /usr/s rc/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0" locked from /usr/src/sy s/dev/sound/pcm/sound.c:134 /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0" locke
Re: build broken
Eric J. Chet wrote: Hello I just tried a -current buildworld which failed: --- "/usr/src/gnu/usr.bin/groff/tmac/Makefile", line 2: warning: duplicate script for target "-s" ignored make: don't know how to make doc-common-s. Stop --- Anybody else seeing this? Thanks, Eric Yes, buildworld is broken here for me as well. I have not had much time to look into it, I have not seen any other mention of the problem besides yours, and in UPDATING I only see a notification for a possible problem on Alphas. I do believe people are working on it, however. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
perl5.6.1
Hi, It would be nice to see this version of perl in -CURRENT. It would help ease the development of mod_perl-2.0 by not having to install the port and it just makes sense considering the bleeding-edge of the rest of the system. Thanks, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Patch for critical_enter()/critical_exit() & interrupt assem
Can someone please end this nightmare? If you've reviewed the patch and found substantive reason to contest it then speak now else the patch should be commited today so that forward progress can continue. I mean, cut the crap and state the facts you see about the code or sit in silence while those who do know the facts work them out. To bitch and moan because you assume it might interrupt someone elses work is as antiproductive as anything can be. From what I've seen I think Matt should be allowed to commit. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current issue: libtool hell
I just pulled php4 from cvs and found that libtool version 1.4 is required for the build. I know the popular response is to say "shut up and code," but I'm not afraid to admit that libtool is way over my head. I just hope some sympathetic genius sees this and decides they're not above tackling this horrible nightmare of a port. Thanks, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV in current
Rob wrote: > I've tried to copy MAKEDEV to /dev in current. But get the error- > "operation not supported". I must be missing some very basic concept. > Rob. Set NO_MAKEDEV_INSTALL=true in /etc/make.conf and make tweaks to /etc/rc.devfs for /dev permissions on -current. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
perl troubles
Hello, I did a fresh install of 5.0-CURRENT-20020519-JPSNAP from snapshots.jp.freebsd.org to see how it would go. The installation went fine and so did the building and installation of world, but now I've found a couple problems. Is anyone doing a fix for /usr/libexec/locate.updatedb, when run it fails with: perl: not found. Also, the perl5 port will not build, I get the following output after it's already patched and configured up to this point: ===> Building for perl-5.6.1_2 ===> Extracting for perl-5.6.1_2 >> No MD5 checksum file. ===> Patching for perl-5.6.1_2 /usr/bin/sed -e 's|%%PREFIX%%|/usr/local|g;' -e 's|%%PERL_VER%%|5.6.1|g;' -e ' s|%%PERL_VERSION%%|5.6.1|g;' -e 's|%%PERL_ARCH%%|mach|g;' /usr/ports/lang/perl 5/work/perl-5.6.1/files/use.perl > /usr/ports/lang/perl5/work/perl-5.6.1/work/u se.perl sed: /usr/ports/lang/perl5/work/perl-5.6.1/files/use.perl: No such file or direc tory *** Error code 1 Stop in /usr/ports/lang/perl5/work/perl-5.6.1. *** Error code 1 Stop in /usr/ports/lang/perl5. I can send the full output if needed. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86-4-libraries build error
I'm getting the following error on a just built -current, which was a fresh install of 5.0-CURRENT-20020519-JPSNAP: installing in lib/XThrStub... rm -f UIThrStubs.o LD_LIBRARY_PATH=../../exports/lib cc -c -O -pipe-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../.. -I../../exports/include -DCSRG_BASED -DFUNC PROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DM ALLOC_0_RETURNS_NULL-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith-I. ./.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHR EADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -fPI C UIThrStubs.c UIThrStubs.c:102: alias arg not a string UIThrStubs.c:103: alias arg not a string UIThrStubs.c:104: alias arg not a string UIThrStubs.c:105: alias arg not a string UIThrStubs.c:106: alias arg not a string UIThrStubs.c:107: alias arg not a string UIThrStubs.c:108: alias arg not a string UIThrStubs.c:109: alias arg not a string UIThrStubs.c:110: alias arg not a string UIThrStubs.c:111: alias arg not a string UIThrStubs.c:113: alias arg not a string UIThrStubs.c:114: alias arg not a string UIThrStubs.c:115: alias arg not a string UIThrStubs.c:131: warning: `_Xthr_self_stub_' defined but not used UIThrStubs.c:139: warning: `_Xthr_zero_stub_' defined but not used *** Error code 1 Stop in /usr/ports/x11/XFree86-4-libraries/work/xc/lib/XThrStub. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What is Tinderbox?
rob wrote: > Pardon my ignorant question. What is Tinderbox? My guess is that its a > special machine for doing some testing. Rob. A tinderbox is a machine dedicated to building something big and complex. Here's a good example from the mozilla project. http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey-Ports Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4-libraries build error
Dag-Erling Smorgrav wrote: > Alfred Perlstein <[EMAIL PROTECTED]> writes: > >>* Peter Wemm <[EMAIL PROTECTED]> [020530 01:01] wrote: >> >>>gcc-3.1 appears to have broken >>>#pragma weak foo = bar >> >>What's the correct way to do this now? > > > #pragma weak foo = "bar" > > as you'd have guessed if you'd bothered to read the error message and > look at the code > > DES Amazing, the obvious. Now I get this: rm -f ../../../../../lib/GL/mesa/src/translate.o unshared/../../../../../lib/GL/mesa/src/translate.o LD_LIBRARY_PATH=../../../../../exports/lib cc -c -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../../../../../exports/include/X11 -I../../../../../include/extensions -I../../../../../extras/Mesa/src/OSmesa -I../../../../../extras/Mesa/src -I../../../../../extras/Mesa/include -I../../../../.. -I../../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI -DMALLOC_0_RETURNS_NULL ../../../../../lib/GL/mesa/src/translate.c -o unshared/../../../../../lib/GL/mesa/src/translate.o Assembler messages: FATAL: can't create unshared/../../../../../lib/GL/mesa/src/translate.o: No such file or directory *** Error code 1 Stop in /usr/ports/x11/XFree86-4-libraries/work/xc/lib/GL/mesa/src/OSmesa. The make needs to go back one more level: unshared/../../../../../../lib/GL/mesa/src/translate.o How to do this, I do not know. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Two Install Issues
Since -current uses devfs now is the remaking devices step still needed? When promted to enter the root password there is no visible indicator that it's time to type. Are these PR material? Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
