Re: Using ipfw in current branch
> Hello again, > > Please disregard the email below, I realized I wasn't using that kernconf > file. So I re-added the following lines to the latest GENRIC kernconf file: > > # JD > options IPFILTER# ipfilter or something > options IPDIVERT# enable nat > options IPFILTER_LOG# something else too > options IPFILTER_DEFAULT_BLOCK # Block all packets by default > [snip] > Ideas? > Here is the updated kernconf link: > http://www.dictos.com/AHAB > > Thanks, > -Jason > Try reading /usr/src/UPDATING (its near the top, but read the whole thing anyway - it'll be good for you). Also, ipfw and ipfilter are not the same thing. Brian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB Keyboard questions
Thanks for the answer, I have been reading that page and I have the keyboard working, but I fail to see how this will help a user that only has a USB Keyboard that wants to use FreeBSD5.1 and is unable to install it due to the lack of USB support from the start. And I still would like to know if its my keyboard that is out of sync with the USB spec since it will add letters when I write like . "This should read like this" but can end up like "Thisi should reaed likek this" Thanks Peter - Original Message - From: "Andre Guibert de Bruet" <[EMAIL PROTECTED]> To: "Peter" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, October 19, 2003 5:08 PM Subject: Re: USB Keyboard questions > > On Sat, 18 Oct 2003, Peter wrote: > > > I have been trying to install FreeBSD 5.1 with a Logitech USB > > keyboard. But I have been unable to do that since it looks like > > FreeBSD 5.1 doesnt recognize the keyboard when it hasnt loaded the > > kernel. I then tried to install FreeBSD 4.8 and it worked like a charm > > with the USB keyboard. > > > > My first question is; Why isnt there support for a USB Keyboard during > > the installation of FreeBSD 5.1 and during the boot up process as > > well? I am unable to use it in the boot screen of FreeBSD 5.1. > > > > My second question is; I have been able to get the usb keyboard > > working in FreeBSD after help in the question mailing list, but when I > > use it I tend to every now and then get the same character again, this > > happens most often when im typing fast. I gues this is common knowledg > > but since Im new in current and new to using USB Keyboard in FreeBSD > > and I havent found much searching in Google. Is there a way to stop it > > or is it a bug in the USB source for FreeBSD, or just me. Mostly > > intrested in the status of this. > > > > Im running FreeBSD 5.1 release #0 with Generic kernel. > > Motherboard: Abit KD7 > > CPU: AMD Baraton > > Keyboard: Logitech cordless comfort > > All the information you need to set it up is in the ukbd(4) manpage. > > Regards, > > > Andre Guibert de Bruet | Enterprise Software Consultant > > > Silicon Landmark, LLC. | http://siliconlandmark.com/> > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Using ipfw in current branch
Hello again, Please disregard the email below, I realized I wasn't using that kernconf file. So I re-added the following lines to the latest GENRIC kernconf file: # JD options IPFILTER# ipfilter or something options IPDIVERT# enable nat options IPFILTER_LOG# something else too options IPFILTER_DEFAULT_BLOCK # Block all packets by default # JD Sound device pcm And I also uncommented the following since I have a dual proc: # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I Now when I compile the kernel using make buildkernel KERNCONF=AHAB I get the following error: cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c: In function `fr_check_wrapper': /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:319: error: `PFIL_OUT' undeclared (first use in this function) /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:319: error: (Each undeclared identifier is reported only once /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:319: error: for each function it appears in.) /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c: In function `fr_check_wrapper6': /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:329: error: `PFIL_OUT' undeclared (first use in this function) /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c: In function `iplattach': /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:376: warning: unused variable `ph_inet' /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:378: warning: unused variable `ph_inet6' /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c: At top level: /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:317: warning: `fr_check_wrapper' defined but not used /usr/src/sys/contrib/ipfilter/netinet/ip_fil.c:327: warning: `fr_check_wrapper6' defined but not used *** Error code 1 Stop in /usr/obj/usr/src/sys/AHAB. *** Error code 1 Stop in /usr/src. *** Error code 1 Ideas? Here is the updated kernconf link: http://www.dictos.com/AHAB Thanks, -Jason > Hi All, > > Here is what I get when I attempt to use any ipfilter type operations: > > [EMAIL PROTECTED]:/home/jason# ipfw flush > Are you sure? [yn] y > > ipfw: setsockopt(IP_FW_FLUSH): Protocol not available > [EMAIL PROTECTED]:/home/jason# > > Has the kernel configuration paramaters changed since the official cut of > 5.1? > Before the upgrade i could use ipfw. > > Here is a link to my kernconf file: > http://www.dictos.com/JASONKERN > > Thanks, > -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DRM SMPng locking for review
On Thu, 2003-10-16 at 23:03, Eric Anholt wrote: > I've been working on locking of the DRM, based off of the work that was > already done for linux and ported to BSD. I think the current locking > was wrong, including that it used lockmgr and simplelocks on -stable > when as far as I know it was unnecessary. Also, I had marked the IRQ > handlers MPSAFE without understanding the issue really, so IRQs could > get missed. Here's a patch, which I hope someone can review because I > don't trust myself at all. > http://people.freebsd.org/~anholt/dri/files/drm-locking-2.diff > > It's against DRI CVS, as I haven't merged to FreeBSD in a while. You > can get it using the instructions at: > http://dri.sourceforge.net/cgi-bin/moin.cgi/CVS > If you don't want to build the whole tree, you can just: > > cd xc > patch -p0 < ~/drm-locking-2.diff > cd programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel > ln -s ../../../shared/drm/kernel/*.[ch] ./ > > Quick question: If open returns an error, close doesn't get called, does > it? Well, I went ahead and made a bunch of fixes and committed it. Should anyone want to review the code, the same steps with the patch step removed should do it. I'll probably bring it over to -current some time soon. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Using ipfw in current branch
Hi All, Here is what I get when I attempt to use any ipfilter type operations: [EMAIL PROTECTED]:/home/jason# ipfw flush Are you sure? [yn] y ipfw: setsockopt(IP_FW_FLUSH): Protocol not available [EMAIL PROTECTED]:/home/jason# Has the kernel configuration paramaters changed since the official cut of 5.1? Before the upgrade i could use ipfw. Here is a link to my kernconf file: http://www.dictos.com/JASONKERN Thanks, -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Usb weirdness on latest get
Hi All, Using 3 day old current branch, usb keyboard acting funny. Whenever I type at normal speeds on my wireless logitech usb keyboard, the text appears to overflow and more characters get output then typed. Below is what happens when I type normally: Here's whaht thahppenes when I type enormally w ith hthte eusb keyboard Is there anyway to debug this problem? -Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help saving my system
Ah, such a strong comment from such a strong member. I would have thought you were to high to stoop that low? But I guess it's good to be flamed for being honest? is it not? --On Sunday, October 19, 2003 8:45 PM +0200 Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: "Scott M. Likens" <[EMAIL PROTECTED]> writes: Comments anyone? Yes: you're an idiot. Go play somewhere else. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" --- The word bipartisan usually means some larger-than-usual deception is being carried out. - George Carlin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Anyone working on a port of OpenBSD's CARP?
Hi, I was just wondering if anyone was currently having a look at the possibility of porting OpenBSD's CARP. I have a bit of free time on my hands but wouldn't want to duplicate anyone's work... Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: -march athlon breaks my networking was: ip stack broken?
Roger Wilco! Andre Guibert de Bruet wrote: On Sun, 19 Oct 2003, slave-mike wrote: I realized that my /etc/make.conf was set to use -O0 -march athlon for kernel builds. After removing the COPTS and CPU stuff form /etc/make.conf my kernel's networking now works fine. Any clue as to why -march athlon breaks my networking? Could you change only one variable at a time? Start off by using -march=athlon and -O to eliminate the -march argument. As Kris pointed out, kernels are usually not built with -O0. Regards, Andre Guibert de Bruet | Enterprise Software Consultant > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ip stack broken?
Follows is my arp table entries and interface while running a -current kernel. My system can see the default gateway etc, and appears to be transmitting packets (based on activity of hub lights), but does not seem to be receiving them back or knowing they are received back beyond the arp/rarp packets or it just plain eats them. :) 192.168.0.1 is my default gw I have tried both fxp0 and dc0. I have tried both with and without vmnet being loaded. ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] dc0: flags=8943 mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX ) status: active mjoyner wrote: It works fine with a 5.1 kernel. Doug White wrote: On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] dc0: flags=8943 mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX ) status: active ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: More ULE bugs fixed.
On Fri, 17 Oct 2003, Jeff Roberson wrote: > On Fri, 17 Oct 2003, Bruce Evans wrote: > > > How would one test if it was an improvement on the 4BSD scheduler? It > > is not even competitive in my simple tests. > > ... > > At one point ULE was at least as fast as 4BSD and in most cases faster. > This is a regression. I'll sort it out soon. How much faster? > > Test 5 for fair scheduling related to niceness: > > > > for i in -20 -16 -12 -8 -4 0 4 8 12 16 20 > > do > > nice -$i sh -c "while :; do echo -n;done" & > > done > > time top -o cpu > > > > With SCHED_ULE, this now hangs the system, but it worked yesterday. Today > > it doesn't get as far as running top and it stops the nfs server responding. > 661 root 112 -20 900K 608K RUN 0:24 27.80% 27.64% sh > 662 root 114 -16 900K 608K RUN 0:19 12.43% 12.35% sh > 663 root 114 -12 900K 608K RUN 0:15 10.66% 10.60% sh > 664 root 114 -8 900K 608K RUN 0:11 9.38% 9.33% sh > 665 root 115 -4 900K 608K RUN 0:10 7.91% 7.86% sh > 666 root 1150 900K 608K RUN 0:07 6.83% 6.79% sh > 667 root 1154 900K 608K RUN 0:06 5.01% 4.98% sh > 668 root 1158 900K 608K RUN 0:04 3.83% 3.81% sh > 669 root 115 12 900K 608K RUN 0:02 2.21% 2.20% sh > 670 root 115 16 900K 608K RUN 0:01 0.93% 0.93% sh Perhaps the bug only affects SMP. The above is for UP (no CPU column). I see a large difference from the above, at least under SMP: %CPU tapers off to 0 at nice 0. BTW, I just noticed that SCHED_4BSD never really worked for the SMP case. sched_clock() is called for each CPU, and for N CPU's this has the same effect as calling sched_clock() N times too often for 1 CPU. Calling sched_clock() too often was fixed for the UP case in kern_synch.c 1.83 by introducing a scale factor. The scale factor is fixed so it doesn't help for SMP. > I think you cvsup'd at a bad time. I fixed a bug that would have caused > the system to lock up in this case late last night. On my system it > freezes for a few seconds and then returns. I can stop that by turning > down the interactivity threshold. No, I tested with an up to date kernel (sched_ule.c 1.65). Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: samba 3 on CURRENT and net.inet.tcp.blackhole
On 14 Oct, Michal wrote: > Hello, > I have a problem with samba 3.0. > I had to reinstall FreeBSD-CURRENT after known problems with ATAng and > atapicam (beginning of September(?)), since then I can't set > net.inet.tcp.blackhole=2 in /etc/sysctl.conf. If I add the option to > sysctl then > samba will hung until I press ^C. If I boot without this option then samba > starts fine. However running now > sysctl net.inet.tcp.blackhole=2 prevent smbclient from running. I still > will be > able to connect to smb shere from another computer. How long did you wait before interrupting samba? My suspicion is that it is attempting to connect to a port that doesn't have a listener, and it is relying on receiving the ICMP unreachable to cause a connect() call to fail with ECONNREFUSED before it makes a connection attempt to another port that succeeds. If this is the situation, then the connect() call should eventually fail with ETIMEDOUT if you wait long enough. You might try disabling net.inet.tcp.blackhole and enabling net.inet.tcp.log_in_vain instead. That will tell you if samba is attempting to connect to a port without a listener when it starts up and might give you a hint about possible configuration changes that you could make so that you can re-enable net.inet.tcp.blackhole. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[current tinderbox] failure on amd64/amd64
___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[current tinderbox] failure on sparc64/sparc64
TB --- 2003-10-12 11:26:10 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-10-12 11:26:10 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-10-12 11:26:10 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-10-12 11:28:02 - building world TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: populating >>> /home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything.. TB --- 2003-10-12 12:22:29 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Oct 12 12:22:29 GMT 2003 >>> Kernel build for GENERIC completed on Sun Oct 12 12:31:39 GMT 2003 TB --- 2003-10-12 12:31:39 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/conf TB --- /usr/bin/make -B LINT TB --- 2003-10-12 12:31:39 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Oct 12 12:31:39 GMT 2003 [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/crypto/des/des_ecb.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/crypto/des/des_setkey.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/crypto/rijndael/rijndael-alg-fst.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/crypto/rijndae
Re: Sched_Ule
On Thursday 09 October 2003 10:00 pm, Evan Dower wrote: > Is nvidia.ko still loaded in the kernel? No it isn't. In fact, I completely deinstalled it and had a reboot since then. -- Jonathan Fosburgh AIX and Storage Administrator UT MD Anderson Cancer Center Houston, TX ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[releng_5_1 tinderbox] failure on i386/i386
TB --- mkdir /home/des/tinderbox/RELENG_5_1/i386 TB --- mkdir /home/des/tinderbox/RELENG_5_1/i386/i386 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: no partition entries for /dev/ad3
On Wed, Oct 08, 2003 at 11:20:16AM -0700, Andrew P. Lentvorski, Jr. wrote: > I can only fix one of those things. ;) To whomever wrote the Fdisk and > Label editor in sysinstall: Thanks. You did a good job, and I thank you > for it. Hrm, perhaps we should rip it out and maintain it as a separate tool if libh kicks off. BMS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kernel build breaks in dev/cardbus
Hi, a buildkernel from a fresh cvsup breaks with these errors: cc -O -pipe -mcpu=pentiumpro -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -finline-limit=15000 -fno-common -g -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/dev/cardbus/cardbus.c /usr/src/sys/dev/cardbus/cardbus_cis.c: In function `decode_tuple_copy': /usr/src/sys/dev/cardbus/cardbus_cis.c:205: error: invalid application of `sizeof' to an incomplete type /usr/src/sys/dev/cardbus/cardbus_cis.c:209: error: invalid application of `sizeof' to an incomplete type /usr/src/sys/dev/cardbus/cardbus_cis.c:214: error: invalid use of undefined type `struct cis_tupleinfo' /usr/src/sys/dev/cardbus/cardbus_cis.c:214: error: dereferencing pointer to incomplete type /usr/src/sys/dev/cardbus/cardbus_cis.c:215: error: invalid use of undefined type `struct cis_tupleinfo' /usr/src/sys/dev/cardbus/cardbus_cis.c:215: error: dereferencing pointer to incomplete type /usr/src/sys/dev/cardbus/cardbus_cis.c:216: error: invalid use of undefined type `struct cis_tupleinfo' /usr/src/sys/dev/cardbus/cardbus_cis.c:216: error: dereferencing pointer to incomplete type /usr/src/sys/dev/cardbus/cardbus_cis.c:217: error: invalid use of undefined type `struct cis_tupleinfo' /usr/src/sys/dev/cardbus/cardbus_cis.c:217: error: dereferencing pointer to incomplete type /usr/src/sys/dev/cardbus/cardbus_cis.c: In function `cardbus_cis_free': /usr/src/sys/dev/cardbus/cardbus_cis.c:1124: error: invalid use of undefined type `struct cis_tupleinfo' /usr/src/sys/dev/cardbus/cardbus_cis.c:1124: error: dereferencing pointer to incomplete type /usr/src/sys/dev/cardbus/cardbus.c:380: error: `card_cis_read_desc' undeclared here (not in a function) /usr/src/sys/dev/cardbus/cardbus.c:380: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:380: error: (near initialization for `cardbus_methods[27].desc') /usr/src/sys/dev/cardbus/cardbus.c:380: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:380: error: (near initialization for `cardbus_methods[27]') /usr/src/sys/dev/cardbus/cardbus.c:381: error: `card_cis_free_desc' undeclared here (not in a function) /usr/src/sys/dev/cardbus/cardbus.c:381: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:381: error: (near initialization for `cardbus_methods[28].desc') /usr/src/sys/dev/cardbus/cardbus.c:381: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:381: error: (near initialization for `cardbus_methods[28]') /usr/src/sys/dev/cardbus/cardbus.c:384: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:384: error: (near initialization for `cardbus_methods[29]') /usr/src/sys/dev/cardbus/cardbus.c:385: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:385: error: (near initialization for `cardbus_methods[30]') /usr/src/sys/dev/cardbus/cardbus.c:386: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:386: error: (near initialization for `cardbus_methods[31]') /usr/src/sys/dev/cardbus/cardbus.c:387: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:387: error: (near initialization for `cardbus_methods[32]') /usr/src/sys/dev/cardbus/cardbus.c:388: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:388: error: (near initialization for `cardbus_methods[33]') /usr/src/sys/dev/cardbus/cardbus.c:389: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:389: error: (near initialization for `cardbus_methods[34]') /usr/src/sys/dev/cardbus/cardbus.c:390: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:390: error: (near initialization for `cardbus_methods[35]') /usr/src/sys/dev/cardbus/cardbus.c:391: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:391: error: (near initialization for `cardbus_methods[36]') /usr/src/sys/dev/cardbus/cardbus.c:392: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:392: error: (near initialization for `cardbus_methods[37]') /usr/src/sys/dev/cardbus/cardbus.c:394: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:394: error: (near initialization for `cardbus_methods[38]') *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140
Re: D-Link DWL-520+
On Mon, 6 Oct 2003, tokza wrote:
> On Monday 06 October 2003 03:26, Marcos Biscaysaqu wrote:
> > That wireless card has Texas Instrument chipset and doesn't work on
> > freebsd, I have got a driver for linux but is very dodgy.
> > I wont recomend you use this wireless card.
> >
>
> The only reason to talk about this card is it's name, very similar to DWL-520
> which works perfect with freebsd (as mailing lists says). Only one little
> plus ("+") makes everything sucks :-)
> Tomorrow I'll go to shop for moneyback...
It could be worse. Some have changed the chipset and only changed the rev
number. Box, etc. are identical between the old and new model :-/
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SiI3112 SATA controller problems - status
Søren, The SATA seems better, but is still not working. I tried the Oct 5 snapshot, doing a clean install. I CVSup'd and did make buildworld make buildkernel KERNCONF=GENERIC make installkernel KERNCONF=GENERIC reboot to single user mount -a swapon -a mergemaster -p make installworld System has the same DMA write problems. In this recent case it was installing termcap. I tried the Oct 1 snapshot and it was the same, it errored in installworld installing tar. The SATA is stabler as I can buildworld, but not stable enough to handle the installworld copies. Here is what I copied from the console after it went into the debugger: spec_getpages I/O Read failure(error=5) vm_fault: pager read error panic: initiate_write_inodeblock_ufs2: already started Let me know if you want more information. I will have to reinstall to get a dmesg, if you want a new one. -Derek At 04:09 PM 9/30/2003 -0500, Derek Ragona wrote: Great news to hear Søren. Do you know when a snapshot with the fix will be available? Since I cannot complete a buildworld using the SATA drive without the fix. Thanks for the fix. -Derek At 10:06 PM 9/30/2003 +0200, Soren Schmidt wrote: I have now found a way to reproduce the DMA problems some setups seems to be having with the SiI3112A SATA chip. Now, if I use real SATA drives, (and I mean real SATA drives, the WD Raptor fx is not a real SATA device but just a PATA device with a build in PATA->SATA converter chip) it works just fine no matter what I try. If however I use an older PATA drive and a certain PATA->SATA "dongle" (in this case 1 out of 4 samples) I can reproduce the problem pretty easily. This suggests to me that we are looking at a timing problem of sorts the question is where. I'll work on the problem as time permits... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current 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]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cannot build kernel
Il Dom, 2003-10-05 alle 10:03, Matt Douhan ha scritto: > cvsup this morning 5th oct 12.05 PM > > I get the following error during buildkernel > > > cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/ > sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/ > src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -D_KERNEL > -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing > -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding > -Werror /usr/src/sys/dev/usb/usb.c > /usr/src/sys/dev/usb/usb.c: In function `usbioctl': > /usr/src/sys/dev/usb/usb.c:555: warning: assignment from incompatible pointer > type No problem here with revision 1.93 of usb.c cvsup this morning 2003.10.05 10.35am (west Europe time) Regards -- Rionda aka Matteo Riondato G.U.F.I Staff Member (http://www.gufi.org) BSD-FAQ-it Main Developer (http://www.gufi.org/~rionda) GPG key at: http://www.riondabsd.net/riondagpg.asc Sent from: kaiser.sig11.org running FreeBSD-5.1-CURRENT ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SiI3112 SATA controller problems - status
I have now found a way to reproduce the DMA problems some setups seems to be having with the SiI3112A SATA chip. Now, if I use real SATA drives, (and I mean real SATA drives, the WD Raptor fx is not a real SATA device but just a PATA device with a build in PATA->SATA converter chip) it works just fine no matter what I try. If however I use an older PATA drive and a certain PATA->SATA "dongle" (in this case 1 out of 4 samples) I can reproduce the problem pretty easily. This suggests to me that we are looking at a timing problem of sorts the question is where. I'll work on the problem as time permits... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
acd0: WARNING - REQUEST_SENSE recovered from missing interrupt
acd0: WARNING - REQUEST_SENSE recovered from missing interrupt I get that message during boot and it hangs. If I unplug the cd-rom it will boot. Just upgraded world and kernel last night. Justin __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DISCUSSION: /dev/fd%d.%d and /dev/{a}cd%d[ac] to be discontinued ?
Poul-Henning Kamp writes: > > As soon as these uses of cloning code has been removed, I will move > the floppy and CD drivers under GEOM, paving the way for the > significant changes to the buf/VM system which some of you have > already heard rumours about. (more will emerge after BSDcon'03) > > And now comes the bit which I would like to offer for discussion: > > Should we do this for 5.2 instead ? > I think this sounds good. Can you give a hint as to what you mean by the significant buf/VM system changes? Are you talking about removing the vnode detour for drivers and giving drivers who want it access to the struct file? Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: KDE Konsole, crashes, on a SIGABRT...
On Saturday 23 August 2003 22:52, Mike Makonnen wrote: > As far as I know text attachments are still accepted. So, if the > attachment is being stripped either you are sending gziped/uuencoded > attachments or your MUA is not describing it as text. Well, it was described as text/x-diff. Not an officially IANA registered MIME-type, but text/* nonetheless... perhaps the mailing list manager should be configured to be a little less anal. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: ENE 4-in-1 card reader
M. Warner Losh wrote: In message: <[EMAIL PROTECTED]> Lars Eggert <[EMAIL PROTECTED]> writes: : we've got an Asus Pundit here that has an onboard 4-in-1 memory card reader: : : [EMAIL PROTECTED]:16:1:class=0x050100 card=0x17241043 chip=0x05101524 : rev=0x00 : hdr=0x00 : vendor = 'ENE Technology Inc' : class= memory : subclass = flash : : Is there a driver for this under -current yet? What's at device 16.0? [EMAIL PROTECTED]:16:0: class=0x060700 card=0x14111524 chip=0x14111524 rev=0x01 hdr=0x02 vendor = 'ENE Technology Inc' class= bridge subclass = PCI-CardBus Lars -- Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: Slow Boot
What does pciconf -vl show on the affected machine(s)? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Sun, 17 Aug 2003, Bill Moran wrote: > Mike Atamas wrote: > > When my system boots it seems to stall when it gets here: > > > > xa807,0xa400-0xa403,0xa000-0xa007 mem 0xe100-0xe10001ff irq 11 at device 11. > > 0 on pci1 > > ata2: at 0xe100 on atapci0 > > ata3: at 0xe100 on atapci0 > > > > It stalls for about 20-30 seconds and then continues booting. I can not figure out > > what the problem is or how to solve it. Has anyone had similar issues. > > I've seen this on various hardware. I actually have a 200mhz machine sitting here > that has always done this. I've never seen it cause any problems, and I've never > had any suggestions on how to stop it either. > > My best guess is that the chipset responds slowly to probes, thus it takes a while > to get the list of devices from it. However, I've never looked into it any more > than that. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: __fpclassifyd problem
On Sun, Oct 19, 2003 at 03:48:58PM -0700, Kris Kennaway wrote: > On Sun, Oct 19, 2003 at 03:13:41PM -0700, Steve Kargl wrote: > > > I sent in an email *along time ago* about this type > > of problem. See the fallout due to revision 1.24 > > of lib/libc/stdio/findfp.c. IMHO, all shared libraries > > versions should have been bumped in going from 4.x to > > 5.0. > > You don't want to do it before you have to, because this creates more > pain for people when you make a change that breaks backwards compat > (given the policy/preference of only bumping once per major release). > > I'm working on a script that will detect the kind of backwards > compatibility breakage we're seeing here by comparing the symbols in > 4.x and 5.x versions of libraries with the same major revision. We > can then run this once a day/week/whatever somewhere to catch these > problems as soon as they occur in future. > You and I participated in the first go around in the library versioning problem. For one of my attempts to discuss this problem, see http://www.freebsd.org/cgi/getmsg.cgi?fetch=1981830+1986079+/usr/local/www/db/text/2002/freebsd-current/20021103.freebsd-current -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: -march athlon breaks my networking was: ip stack broken?
in /etc/make.conf #CPUTYPE= athlon #COPTFLAGS= -O0 is what is in my /etc/make.conf -march should be -mcpu. sorry!. :) as in "cc -O -pipe -mcpu=pentiumpro ..." Aparantly, when I have my CPUTYPE set to ATHLON, and the build is called with -mcpu=athlon, something is going screwy. I had optimization turned off for some reason or other... don't remember why now, it has been a long time since it's been in there, so it has now been commented out, as has CPUTYPE, when seems to result in a default CPUTYPE of pentiumpro Kris Kennaway wrote: On Sun, Oct 19, 2003 at 03:39:59PM -0400, slave-mike wrote: I realized that my /etc/make.conf was set to use -O0 -march athlon for kernel builds. After removing the COPTS and CPU stuff form /etc/make.conf my kernel's networking now works fine. Any clue as to why -march athlon breaks my networking? That's a syntax error - can you please confirm you meant -march=athlon? Kernels aren't usually built without optimization (-O0). Is there some reason you chose to do that? Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: -march athlon breaks my networking was: ip stack broken?
On Sun, 19 Oct 2003, slave-mike wrote: > I realized that my /etc/make.conf was set to use -O0 -march athlon > for kernel builds. > > After removing the COPTS and CPU stuff form /etc/make.conf my kernel's > networking now works fine. > > Any clue as to why -march athlon breaks my networking? Could you change only one variable at a time? Start off by using -march=athlon and -O to eliminate the -march argument. As Kris pointed out, kernels are usually not built with -O0. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
EIB devices/services
Hi, (Not quite for current@, but that's where leading edge is going on) For the new house we are building I'm looking into EIB. (European Installation Bus). And I'm searching for EIB/IP gateways and applications on FreeBSD. Has anybody used these kinds of tools with FBSD (or Linux) All suggestions are welcom. Thanx, --WjW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: __fpclassifyd problem
On Sun, Oct 19, 2003 at 03:13:41PM -0700, Steve Kargl wrote: > I sent in an email *along time ago* about this type > of problem. See the fallout due to revision 1.24 > of lib/libc/stdio/findfp.c. IMHO, all shared libraries > versions should have been bumped in going from 4.x to > 5.0. You don't want to do it before you have to, because this creates more pain for people when you make a change that breaks backwards compat (given the policy/preference of only bumping once per major release). I'm working on a script that will detect the kind of backwards compatibility breakage we're seeing here by comparing the symbols in 4.x and 5.x versions of libraries with the same major revision. We can then run this once a day/week/whatever somewhere to catch these problems as soon as they occur in future. Kris pgp0.pgp Description: PGP signature
Re: firebird 7 in freebsd cvs appears to be broke
> I downloaded the new firebird-7 port from the freebsd cvs server. Make > will run for about 20-mins then stop with these errors: It works for me (i'm posting via a webmail accessed under Mozilla- firebird-0.7), and there is nothing to see on the bento cluster about this port : http://bento.freebsd.org/errorlogs/ Try to clean all your port build environment. -- -jg. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: __fpclassifyd problem
On Sun, Oct 19, 2003 at 03:05:29PM -0600, Scott Long wrote: > Kris Kennaway wrote: > > > >This symbol is defined in libc.so.5. One way you can see this problem > >is if you are running a 4.x binary that links to libm.so.2 on a 5.x > >system, because libm has the same version number in 5.x but is not > >binary compatible. So the 4.x binary links to libc.so.4 and > >libm.so.2, and the latter is actually a 5.x library that expects to > >have __fpclassifyd resolved by linking with libc.so.5. Is it the case > >on your system that you have old 4.x binaries installed? > > > >Kris > > We need to resolve this before 5.2 in some fashion. It looks like the > easiest thing to do is bump libm. Is this advisable? > I sent in an email *along time ago* about this type of problem. See the fallout due to revision 1.24 of lib/libc/stdio/findfp.c. IMHO, all shared libraries versions should have been bumped in going from 4.x to 5.0. -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: __fpclassifyd problem
Kris Kennaway wrote: On Sun, Oct 19, 2003 at 09:08:25PM +0200, John Angelmo wrote: Hello I'm trying to install java-checkstyle on my 5.1 system, the system is upto date (p10) but I get this build error: ===[root] /usr/ports/java/java-checkstyle # make ===> Extracting for java-checkstyle-3.1 Checksum OK for checkstyle-src-3.1.tar.gz. ===> Patching for java-checkstyle-3.1 ===> java-checkstyle-3.1 depends on file: /usr/local/bin/ant - found ===> java-checkstyle-3.1 depends on file: /usr/local/diablo-jdk1.3.1/bin/java - found ===> Configuring for java-checkstyle-3.1 ===> Building for java-checkstyle-3.1 /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol "__fpclassifyd" *** Error code 1 Stop in /usr/ports/java/java-checkstyle. What I understand is that the problem is that I can have some stale libs in /usr/lib how can I solve this? This symbol is defined in libc.so.5. One way you can see this problem is if you are running a 4.x binary that links to libm.so.2 on a 5.x system, because libm has the same version number in 5.x but is not binary compatible. So the 4.x binary links to libc.so.4 and libm.so.2, and the latter is actually a 5.x library that expects to have __fpclassifyd resolved by linking with libc.so.5. Is it the case on your system that you have old 4.x binaries installed? Kris We need to resolve this before 5.2 in some fashion. It looks like the easiest thing to do is bump libm. Is this advisable? Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: __fpclassifyd problem
Kris Kennaway wrote: On Sun, Oct 19, 2003 at 09:08:25PM +0200, John Angelmo wrote: Hello I'm trying to install java-checkstyle on my 5.1 system, the system is upto date (p10) but I get this build error: ===[root] /usr/ports/java/java-checkstyle # make ===> Extracting for java-checkstyle-3.1 Checksum OK for checkstyle-src-3.1.tar.gz. ===> Patching for java-checkstyle-3.1 ===> java-checkstyle-3.1 depends on file: /usr/local/bin/ant - found ===> java-checkstyle-3.1 depends on file: /usr/local/diablo-jdk1.3.1/bin/java - found ===> Configuring for java-checkstyle-3.1 ===> Building for java-checkstyle-3.1 /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol "__fpclassifyd" *** Error code 1 Stop in /usr/ports/java/java-checkstyle. What I understand is that the problem is that I can have some stale libs in /usr/lib how can I solve this? This symbol is defined in libc.so.5. One way you can see this problem is if you are running a 4.x binary that links to libm.so.2 on a 5.x system, because libm has the same version number in 5.x but is not binary compatible. So the 4.x binary links to libc.so.4 and libm.so.2, and the latter is actually a 5.x library that expects to have __fpclassifyd resolved by linking with libc.so.5. Is it the case on your system that you have old 4.x binaries installed? Yes I upgraded from 4.8 to 5.1 I now have compat4 installed to /John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: firebird 7 in freebsd cvs appears to be broke
On Sun, Oct 19, 2003 at 02:42:55PM -0600, KroNiC~BSD wrote: > I downloaded the new firebird-7 port from the freebsd cvs server. Make > will run for about 20-mins then stop with these errors: I do not see this on FreeBSD 5.1-CURRENT. Didn't we already establish you had something wrong with your system (i.e. stale headers in /usr/include) that were causing your compilation failures? Kris pgp0.pgp Description: PGP signature
Re: __fpclassifyd problem
On Sun, Oct 19, 2003 at 09:08:25PM +0200, John Angelmo wrote: > Hello > > I'm trying to install java-checkstyle on my 5.1 system, the system is > upto date (p10) but I get this build error: > > ===[root] /usr/ports/java/java-checkstyle # make > ===> Extracting for java-checkstyle-3.1 > >> Checksum OK for checkstyle-src-3.1.tar.gz. > ===> Patching for java-checkstyle-3.1 > ===> java-checkstyle-3.1 depends on file: /usr/local/bin/ant - found > ===> java-checkstyle-3.1 depends on file: > /usr/local/diablo-jdk1.3.1/bin/java - found > ===> Configuring for java-checkstyle-3.1 > ===> Building for java-checkstyle-3.1 > /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol > "__fpclassifyd" > *** Error code 1 > > Stop in /usr/ports/java/java-checkstyle. > > > What I understand is that the problem is that I can have some stale libs > in /usr/lib > how can I solve this? This symbol is defined in libc.so.5. One way you can see this problem is if you are running a 4.x binary that links to libm.so.2 on a 5.x system, because libm has the same version number in 5.x but is not binary compatible. So the 4.x binary links to libc.so.4 and libm.so.2, and the latter is actually a 5.x library that expects to have __fpclassifyd resolved by linking with libc.so.5. Is it the case on your system that you have old 4.x binaries installed? Kris pgp0.pgp Description: PGP signature
firebird 7 in freebsd cvs appears to be broke
I downloaded the new firebird-7 port from the freebsd cvs server. Make will run for about 20-mins then stop with these errors: gmake[4]: Leaving directory `/sandbox/firebird/work/mozilla/content/xsl/public' gmake[3]: Leaving directory `/sandbox/firebird/work/mozilla/content/xsl' gmake[3]: Entering directory `/sandbox/firebird/work/mozilla/content/events' gmake[4]: Entering directory `/sandbox/firebird/work/mozilla/content/events/public' gmake[4]: Leaving directory `/sandbox/firebird/work/mozilla/content/events/public' gmake[4]: Entering directory `/sandbox/firebird/work/mozilla/content/events/src' nsEventListenerManager.cpp c++ -o nsEventListenerManager.o -c -DOSTYPE=\"FreeBSD5\" -DOSARCH=\"FreeBSD\" -I./../../html/base/src -I./../../xul/content/src -I../../../dist/include/xpcom -I../../../dist/include/string -I../../../dist/include/dom -I../../../dist/include/js -I../../../dist/include/locale -I../../../dist/include/gfx -I../../../dist/include/layout -I../../../dist/include/widget -I../../../dist/include/caps -I../../../dist/include/xpconnect -I../../../dist/include/docshell -I../../../dist/include/pref -I../../../dist/include/view -I../../../dist/include/necko -I../../../dist/include/unicharutil -I../../../dist/include/content -I../../../dist/include -I/sandbox/firebird/work/mozilla/dist/include/nspr -I/usr/local/include -I/usr/local/include -I/usr/X11R6/include -fPIC -I/usr/X11R6/include -I/usr/X11R6/include -I/usr/X11R6/include -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-long-long -O -pipe -march=athlon-xp -D_THREAD_SAFE -fshort-wchar -pipe -DNDEBUG -DTRIMMED -ffunction-sections -I/usr/X11R6/include -I/usr/X11R6/include -I/usr/X11R6/include -DMOZILLA_CLIENT -include ../../../mozilla-config.h nsEventListenerManager.cpp In file included from nsEventListenerManager.cpp:69: ../../../dist/include/content/nsINodeInfo.h:324: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. gmake[4]: *** [nsEventListenerManager.o] Error 1 gmake[4]: Leaving directory `/sandbox/firebird/work/mozilla/content/events/src' gmake[3]: *** [libs] Error 2 gmake[3]: Leaving directory `/sandbox/firebird/work/mozilla/content/events' gmake[2]: *** [libs] Error 2 gmake[2]: Leaving directory `/sandbox/firebird/work/mozilla/content' gmake[1]: *** [tier_9] Error 2 gmake[1]: Leaving directory `/sandbox/firebird/work/mozilla' gmake: *** [default] Error 2 *** Error code 2 Thanks in advance -- KroNiC~BSD [EMAIL PROTECTED] -- http://www.fastmail.fm - Send your email first class ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: src/sys/dev/ep if_epvar.h
In message: <[EMAIL PROTECTED]>
Warner Losh <[EMAIL PROTECTED]> writes:
: FreeBSD src repository
:
: Modified files:
: sys/dev/ep if_epvar.h
: Log:
: Finish the removal of the bst/bsh confusion.
:
: Revision ChangesPath
: 1.11 +10 -10src/sys/dev/ep/if_epvar.h
This should fix the tinderbox builds. Sometimes I wish there was a
way to build i386 with a 'wierd' bus_space_{tag,handle}_t such that
you'd get errors when you swap them...
Warner
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: LOR in yesterday CURRENT
On Sun, Oct 19, 2003 at 11:21:47AM +0200, Paolo Pisati wrote: > > ...lock order reversal > 1st 0xc3142a68 vm object (vm object) @ /usr/src/sys/vm/vm_object.c:433 > 2nd 0xc102f110 system map (system map) @ /usr/src/sys/vm/vm_kern.c:328 Harmless. From alc: In general, any LOR involving a system map mutex and a vm object mutex that has a stack trace looking like _mtx_lock_flags() _vm_map_lock() kmem_malloc() page_alloc() slab_zalloc() uma_zone_slab() uma_zalloc_internal() uma_zfree_arg() ... is not a problem. > Stack backtrace: > _mtx_lock_flags(c102f110,0,c0850fb1,148,3) at _mtx_lock_flags+0xba > _vm_map_lock(c102f0b0,c0850fb1,148,c08feb80,2b4) at _vm_map_lock+0x36 > kmem_malloc(c102f0b0,1000,101,d2762aa8,c079a707) at kmem_malloc+0x3a > page_alloc(c103a3c0,1000,d2762a9b,101,c083ab1b) at page_alloc+0x27 > slab_zalloc(c103a3c0,1,8,c08528ff,68c) at slab_zalloc+0xb7 > uma_zone_slab(c103a3c0,1,c08528ff,68c,0) at uma_zone_slab+0xe6 > uma_zalloc_internal(c103a3c0,0,1,0,c101f470) at uma_zalloc_internal+0x3e > bucket_alloc(80,1,c08528ff,70b,0) at bucket_alloc+0x5e > uma_zfree_arg(c101f3c0,d278be04,0,778,60) at uma_zfree_arg+0x2c6 Kris pgp0.pgp Description: PGP signature
Re: -march athlon breaks my networking was: ip stack broken?
On Sun, Oct 19, 2003 at 03:39:59PM -0400, slave-mike wrote: > I realized that my /etc/make.conf was set to use -O0 -march athlon > for kernel builds. > > After removing the COPTS and CPU stuff form /etc/make.conf my kernel's > networking now works fine. > > Any clue as to why -march athlon breaks my networking? That's a syntax error - can you please confirm you meant -march=athlon? Kernels aren't usually built without optimization (-O0). Is there some reason you chose to do that? Kris pgp0.pgp Description: PGP signature
-march athlon breaks my networking was: ip stack broken?
I realized that my /etc/make.conf was set to use -O0 -march athlon for kernel builds. After removing the COPTS and CPU stuff form /etc/make.conf my kernel's networking now works fine. Any clue as to why -march athlon breaks my networking? slave-mike wrote: FYI: here is the output from ifconfig, arp -an, ipv4 routing tables while running the 5.1-RELEASE kernel. dc0: flags=8943 mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX ) status: active ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.1UGSc80dc0 10 link#4 UC 10 vmnet1 10.255.255.255 ff:ff:ff:ff:ff:ff UHLWb 2 58 vmnet1 127.0.0.1 127.0.0.1 UH 11 3250lo0 192.168.0.0ff:ff:ff:ff:ff:ff UHLWb 09dc0 => 192.168.0 link#1 UC 40dc0 192.168.0.100:a0:c5:e6:58:00 UHLW98dc0332 192.168.0.2127.0.0.1 UGHS05lo0 192.168.0.253 00:06:25:54:2a:20 UHLW01dc0 1057 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 4 147dc0 slave-mike wrote: Follows is my arp table entries and interface while running a -current kernel. My system can see the default gateway etc, and appears to be transmitting packets (based on activity of hub lights), but does not seem to be receiving them back or knowing they are received back beyond the arp/rarp packets or it just plain eats them. :) 192.168.0.1 is my default gw I have tried both fxp0 and dc0. I have tried both with and without vmnet being loaded. ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] dc0: flags=8943 mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX ) status: active mjoyner wrote: It works fine with a 5.1 kernel. Doug White wrote: On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] dc0: flags=8943 mtu 1500 inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 ether 00:c0:f0:48:75:62 media: Ethernet autoselect (100baseTX ) status: active ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current 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]"
__fpclassifyd problem
Hello I'm trying to install java-checkstyle on my 5.1 system, the system is upto date (p10) but I get this build error: ===[root] /usr/ports/java/java-checkstyle # make ===> Extracting for java-checkstyle-3.1 >> Checksum OK for checkstyle-src-3.1.tar.gz. ===> Patching for java-checkstyle-3.1 ===> java-checkstyle-3.1 depends on file: /usr/local/bin/ant - found ===> java-checkstyle-3.1 depends on file: /usr/local/diablo-jdk1.3.1/bin/java - found ===> Configuring for java-checkstyle-3.1 ===> Building for java-checkstyle-3.1 /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol "__fpclassifyd" *** Error code 1 Stop in /usr/ports/java/java-checkstyle. What I understand is that the problem is that I can have some stale libs in /usr/lib how can I solve this? /John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help saving my system
"Scott M. Likens" <[EMAIL PROTECTED]> writes: > Comments anyone? Yes: you're an idiot. Go play somewhere else. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [current tinderbox] failure on alpha/alpha
In message: <[EMAIL PROTECTED]> Tinderbox <[EMAIL PROTECTED]> writes: : /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ep/if_ep.c:962: error: invalid type argument of `->' Ooops. That's my bad. Latest sources seem to work great. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PATCH for ATAng
It seems Hiroyuki Aizu wrote: > Hi. > > The original ata_reset() lost ATA-master drive and remove main file system > after suspend/resume. Of cource it occors panic! > I think that the ata_reset() in ata-lowlevel.c is bogus and I can not > understand the code. So I study ATA and rewrite ata_reset() completely. > > New device detect algorism using ata command ATA_IDENTIFY_DEVICE and > ATA_IDENTIFY_PACKET_DEVICE for judge ATA and ATAPI devices. > > This patch works fine with my TOSHIBA Libretto L5. > But not yet test ATAPI devices and ATA-slave channel. > Maybe there is need to adjust wait DELAY time. > > Please test and replace ata_reset(). Hold your horses just a bit please, I suggest that you try to understand the current code first, then we can talk about improving it.. > I hope this solve ATAng troubles. It will probably solve some troubles but I'll bet it will produce quite a few new ones :) Anyhow I'll look at your code asap, but from a quick look it shows that you havn't looked seriously at the existing code, and that is not a good sign in my book sorry... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[current tinderbox] failure on alpha/alpha
TB --- 2003-10-19 16:00:01 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-10-19 16:00:01 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-10-19 16:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-10-19 16:03:04 - building world TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: populating >>> /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything.. TB --- 2003-10-19 17:05:32 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Oct 19 17:05:32 GMT 2003 >>> Kernel build for GENERIC completed on Sun Oct 19 17:17:18 GMT 2003 TB --- 2003-10-19 17:17:18 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src/sys/alpha/conf TB --- /usr/bin/make -B LINT TB --- 2003-10-19 17:17:18 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Oct 19 17:17:18 GMT 2003 [...] /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ep/if_ep.c:962: error: invalid type argument of `->' /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ep/if_ep.c:963: error: invalid type argument of `->' /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ep/if_ep.c:964: error: invalid type argument of `->' /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ep/if_ep.c:965: error: invalid type argument of `->' /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ep/if_ep.c:967: error: invalid type argument of `->' /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ep/if_ep.c:968: error: invalid type argument of `->' /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ep/if_ep.c:969: error: invalid type argument of `->' /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ep/if_ep.c:970: error: invalid type argument of `->' *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/LINT. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. TB --- 2003-10-19 17:20:52 - TB --- /usr/bin/make returned exit code 1 TB --- 2003-10-19 17:20:52 - TB --- ERROR: failed to build lint kernel TB --- 2003-10-19 17:20:52 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: binaries installed mult. times / no symlinks ?
Or try and figure out a way to get UPX to work on *BSD - Original Message - From: "Q" <[EMAIL PROTECTED]> To: "Bjoern A. Zeeb" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, October 19, 2003 5:20 AM Subject: Re: binaries installed mult. times / no symlinks ? > If you had checked the link count you would have seen that the binaries > you mentioned are actually not installed multiple times, but are "hard > linked" under multiple names, and therefore only take up the space of a > single instance of the file. If these binary files are located on the > same filesystem it is preferable to hardlink rather than symlink them. > I'm not sure if you noticed, but deleting a file with a link count > greater than one will not free up any space, so deleting them is > fruitless unless to plan to delete all of the references. > > If you want something really small, check out the picobsd project on the > freebsd website. > > Seeya...Q > > On Sun, 2003-10-19 at 18:52, Bjoern A. Zeeb wrote: > > > Hi, > > > > I had been going through /usr/bin to see what I would need for a very > > small installation and noticed that there are binaries > > installed multiple times with different names of course. > > > > My question now would be if symlinking wouldn't suffice ? From those > > that I had not deleted I remember the following duplicates that most > > likely are not all of those exist... > > > > Mail -> mail > > Mail -> mailx > > less -> more > > awk -> nawk > > nvi -> nview > > cksum -> sum > > reset -> tset > > nvi -> vi > > nvi -> view > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > 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]"
Re: 5.1-CURRENT rebooting (multile systems) -- How to troubleshoot?
Andre Guibert de Bruet wrote: On Sat, 18 Oct 2003, Tom Parquette wrote: My question is, if the system fails (I'm assuming these are panics) how do I get the machine to NOT automatically reboot so I can copy down the failure information? (Unless these are logged somewhere I have not found yet.) Try hooking up a serial console and logging a system run with "boot -v", overnight. Make sure that you have all of the kernel debug options in GENERIC in your kernel as they will provide insight that can help trace the problem. Additionally, set your kernel up for debugging. This will allow you to get a great deal of information after a crash. This section of the developer's handbook will talk you through it: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-CURRENT rebooting (multile systems) -- How to troubleshoot?
On Sat, 18 Oct 2003, Tom Parquette wrote: > My question is, if the system fails (I'm assuming these are panics) how > do I get the machine to NOT automatically reboot so I can copy down the > failure information? (Unless these are logged somewhere I have not > found yet.) Try hooking up a serial console and logging a system run with "boot -v", overnight. Make sure that you have all of the kernel debug options in GENERIC in your kernel as they will provide insight that can help trace the problem. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB Keyboard questions
On Sat, 18 Oct 2003, Peter wrote: > I have been trying to install FreeBSD 5.1 with a Logitech USB > keyboard. But I have been unable to do that since it looks like > FreeBSD 5.1 doesnt recognize the keyboard when it hasnt loaded the > kernel. I then tried to install FreeBSD 4.8 and it worked like a charm > with the USB keyboard. > > My first question is; Why isnt there support for a USB Keyboard during > the installation of FreeBSD 5.1 and during the boot up process as > well? I am unable to use it in the boot screen of FreeBSD 5.1. > > My second question is; I have been able to get the usb keyboard > working in FreeBSD after help in the question mailing list, but when I > use it I tend to every now and then get the same character again, this > happens most often when im typing fast. I gues this is common knowledg > but since Im new in current and new to using USB Keyboard in FreeBSD > and I havent found much searching in Google. Is there a way to stop it > or is it a bug in the USB source for FreeBSD, or just me. Mostly > intrested in the status of this. > > Im running FreeBSD 5.1 release #0 with Generic kernel. > Motherboard: Abit KD7 > CPU: AMD Baraton > Keyboard: Logitech cordless comfort All the information you need to set it up is in the ukbd(4) manpage. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: binaries installed mult. times / no symlinks ?
On Sun, 19 Oct 2003, David Malone wrote: > On Sun, Oct 19, 2003 at 08:52:59AM +, Bjoern A. Zeeb wrote: > > My question now would be if symlinking wouldn't suffice ? > > All of the programs you list are actually hardlinks to one another. *aarrrggg* should have had another look at it this morning after some minutes of sleep. > If you run "ls -li" on them, you will see that they have the same > inode number, and are consequently the same file. yes. of course. I should recheck the way I had copied them into my image. Must have used cp -p this night instead of tar -cpf - | tar -xpf - -C ... or s.th. like this. That's most likely the problem I hadn't seen a link count > 1 because I didn't look at the original installation: noc:~/install-20031018/usr/bin# ls -i ex nex nvi nview vi view 47625 ex 47625 nex 47625 nvi 47625 nview 47625 vi 47625 view but noc:/mnt/usr/bin# ls -i ex nex nvi nview vi view 346 ex 246 nex 240 nvi 239 nview 114 vi 113 view many thanks for all the answers. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ tech support excuse #226: Fatal error right in front of screen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
still panic
cvsup'd 19 Oct 2003 in the morning (jakarta time),
> uname -a
FreeBSD ipv6.ppk.itb.ac.id 5.1-CURRENT FreeBSD 5.1-CURRENT #3: Sun Oct 19 21:25:
57 WIT 2003 root@:/usr/obj/usr/src/sys/PPK i386
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xdeadc0de
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0554bd8
stack pointer = 0x10:0xd5b83900
frame pointer = 0x10:0xd5b83900
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 917 (cvsup)
trap number = 12
panic: page fault
Uptime: 5m26s
Dumping 255 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
---
Reading symbols from /usr/obj/usr/src/sys/PPK/modules/usr/src/sys/modules/acpi/a
cpi.ko.debug...done.
Loaded symbols for /usr/obj/usr/src/sys/PPK/modules/usr/src/sys/modules/acpi/acp
i.ko.debug
Reading symbols from /boot/kernel/daemon_saver.ko...done.
Loaded symbols for /boot/kernel/daemon_saver.ko
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb)
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc04ecd5c in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc04ed0e7 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3 0xc067b086 in trap_fatal (frame=0xd5b838c0, eva=0)
at /usr/src/sys/i386/i386/trap.c:820
#4 0xc067ad22 in trap_pfault (frame=0xd5b838c0, usermode=0, eva=3735929054)
at /usr/src/sys/i386/i386/trap.c:734
#5 0xc067a8dd in trap (frame=
{tf_fs = -709361640, tf_es = -1068433392, tf_ds = -1066270704, tf_edi = -1
066676471, tf_esi = -559038242, tf_ebp = -709347072, tf_isp = -709347092, tf_ebx
= -709346844, tf_edx = -559038242, tf_ecx = 0, tf_eax = -559038242, tf_trapno =
12, tf_err = 0, tf_eip = -1068151848, tf_cs = 8, tf_eflags = 66118, tf_esp = -7
09346872, tf_ss = -1068442863}) at /usr/src/sys/i386/i386/trap.c:419
#6 0xc066b5e8 in calltrap () at {standard input}:102
#7 0xc050db11 in kvprintf (fmt=0xc06bcf09 " @ %s:%d",
func=0xc050d4b0 , arg=0xd5b839e4, radix=10,
ap=0xd5b83a30 "ÚslÀW\001") at /usr/src/sys/kern/subr_prf.c:669
#8 0xc050d42e in vsnprintf (str=0xc0726380 "mtx_lock() of spin mutex ",
size=0, format=0x0, ap=0x0) at /usr/src/sys/kern/subr_prf.c:414
#9 0xc04ed001 in panic (fmt=0xc06bceee "mtx_lock() of spin mutex %s @ %s:%d")
at /usr/src/sys/kern/kern_shutdown.c:511
#10 0xc04e3156 in _mtx_lock_flags (m=0xc43c3690, opts=0,
file=0xc06c73da "/usr/src/sys/netinet/ip_input.c", line=343)
at /usr/src/sys/kern/kern_mutex.c:332
#11 0xc057aa0b in ip_forward_cacheinval ()
at /usr/src/sys/netinet/ip_input.c:343
#12 0xc0577fee in in_addroute (v_arg=0xc44ab560, n_arg=0x0, head=0xc422c400,
treenodes=0xc4741100) at /usr/src/sys/netinet/in_rmx.c:147
#13 0xc056827b in rtrequest1 (req=11, info=0xd5b83ae8, ret_nrt=0xd5b83b44)
at /usr/src/sys/net/route.c:675
#14 0xc0567cca in rtrequest (req=0, dst=0x0, gateway=0x0, netmask=0x0,
flags=0, ret_nrt=0x0) at /usr/src/sys/net/route.c:477
#15 0xc0567536 in rtalloc1 (dst=0xc433b3d0, report=1, ignflags=0)
at /usr/src/sys/net/route.c:148
#16 0xc0567409 in rtalloc_ign (ro=0xc433b3cc, ignore=0)
at /usr/src/sys/net/route.c:102
#17 0xc0567359 in rtalloc (ro=0x0) at /usr/src/sys/net/route.c:88
#18 0xc0576f71 in in_pcbconnect_setup (inp=0xc433b390, nam=0x0,
laddrp=0xd5b83c2c, lportp=0xd5b83c36, faddrp=0x0, fportp=0x0,
oinpp=0xd5b83c30, td=0xc4720720) at /usr/src/sys/netinet/in_pcb.c:582
#19 0xc058b311 in tcp_connect (tp=0xc433d590, nam=0x0, td=0xc4720720)
at /usr/src/sys/netinet/tcp_usrreq.c:870
#20 0xc058a4d6 in tcp_usr_connect (so=0x0, nam=0xc41b3560, td=0xc4720720)
at /usr/src/sys/netinet/tcp_usrreq.c:378
#21 0xc052a4d1 in soconnect (so=0xc4767000, nam=0x0, td=0x0)
at /usr/src/sys/kern/uipc_socket.c:447
#22 0xc052e628 in kern_connect (td=0xc4720720, fd=0, sa=0xc41b3560)
at /usr/src/sys/kern/uipc_syscalls.c:484
#23 0xc052e583 in connect (td=0x0, uap=0xd5b83d10)
at /usr/src/sys/kern/uipc_syscalls.c:458
#24 0xc067b3c0 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077937148, tf_esi = -10779
37124, tf_ebp = -1077938980, tf_isp = -709345932, tf_ebx = 5, tf_edx = 5999, tf_
ecx = 135435512, tf_eax = 98, tf_trapno = 12, tf_err = 2, tf_eip = 672723791, tf
_cs = 31, tf_eflags = 646, tf_esp = -1077939072, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1009
#25 0xc066b63d in Xint0x80_syscall () at {standard input}:144
-dikshie-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: binaries installed mult. times / no symlinks ?
On Sun, Oct 19, 2003 at 08:52:59AM +, Bjoern A. Zeeb wrote: > My question now would be if symlinking wouldn't suffice ? All of the programs you list are actually hardlinks to one another. If you run "ls -li" on them, you will see that they have the same inode number, and are consequently the same file. > nvi -> nview > nvi -> vi > nvi -> view You can add ex and nex to this list too. David. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: More ULE bugs fixed.
Eirik Oeverby wrote: > As a side note/question: > Is there any way to figure out which ULE version I'm running in a > precompiled kernel? I just nuked my src tree by accident, and am not > sure if i'm on 1.65 or something older.. > > If there is no way, is this perhaps an idea? Try "ident /boot/kernel/kernel | grep sched_ule". Cheers, Maxime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: binaries installed mult. times / no symlinks ?
If you had checked the link count you would have seen that the binaries you mentioned are actually not installed multiple times, but are "hard linked" under multiple names, and therefore only take up the space of a single instance of the file. If these binary files are located on the same filesystem it is preferable to hardlink rather than symlink them. I'm not sure if you noticed, but deleting a file with a link count greater than one will not free up any space, so deleting them is fruitless unless to plan to delete all of the references. If you want something really small, check out the picobsd project on the freebsd website. Seeya...Q On Sun, 2003-10-19 at 18:52, Bjoern A. Zeeb wrote: > Hi, > > I had been going through /usr/bin to see what I would need for a very > small installation and noticed that there are binaries > installed multiple times with different names of course. > > My question now would be if symlinking wouldn't suffice ? From those > that I had not deleted I remember the following duplicates that most > likely are not all of those exist... > > Mail -> mail > Mail -> mailx > less -> more > awk -> nawk > nvi -> nview > cksum -> sum > reset -> tset > nvi -> vi > nvi -> view ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
LOR in yesterday CURRENT
...lock order reversal 1st 0xc3142a68 vm object (vm object) @ /usr/src/sys/vm/vm_object.c:433 2nd 0xc102f110 system map (system map) @ /usr/src/sys/vm/vm_kern.c:328 Stack backtrace: backtrace(c083e674,c102f110,c0851116,c0851116,c0850fb1) at backtrace+0x17 witness_lock(c102f110,8,c0850fb1,148,0) at witness_lock+0x672 _mtx_lock_flags(c102f110,0,c0850fb1,148,3) at _mtx_lock_flags+0xba _vm_map_lock(c102f0b0,c0850fb1,148,c08feb80,2b4) at _vm_map_lock+0x36 kmem_malloc(c102f0b0,1000,101,d2762aa8,c079a707) at kmem_malloc+0x3a page_alloc(c103a3c0,1000,d2762a9b,101,c083ab1b) at page_alloc+0x27 slab_zalloc(c103a3c0,1,8,c08528ff,68c) at slab_zalloc+0xb7 uma_zone_slab(c103a3c0,1,c08528ff,68c,0) at uma_zone_slab+0xe6 uma_zalloc_internal(c103a3c0,0,1,0,c101f470) at uma_zalloc_internal+0x3e bucket_alloc(80,1,c08528ff,70b,0) at bucket_alloc+0x5e uma_zfree_arg(c101f3c0,d278be04,0,778,60) at uma_zfree_arg+0x2c6 swp_pager_meta_free_all(c3142a68,c08508ce,c0850833,21a) at swp_pager_meta_free_a ll+0xf2 swap_pager_dealloc(c3142a68,1,c0852863,104,0) at swap_pager_dealloc+0x11a vm_pager_deallocate(c3142a68,0,c0851a43,260,c08528ff) at vm_pager_deallocate+0x3 d vm_object_terminate(c3142a68,0,c0851a43,1b1,c30e3d20) at vm_object_terminate+0x2 03 vm_object_deallocate(c3142a68,c31006cc,c3142a68,c31006cc,d2762c60) at vm_object_ deallocate+0x371 vm_map_entry_delete(c16cd6e4,c31006cc,c085118c,8a8,c0839c32) at vm_map_entry_del ete+0x3b vm_map_delete(c16cd6e4,0,bfc0,c16cd6e4,c2e02c80) at vm_map_delete+0x383 vm_map_remove(c16cd6e4,0,bfc0,11d,65) at vm_map_remove+0x55 exit1(c2d79980,0,c08391e3,65,d2762d40) at exit1+0x65d sys_exit(c2d79980,d2762d10,c0856d61,3ed,1) at sys_exit+0x41 syscall(002f,2f,bfbf002f,0,) at syscall+0x2c0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (1), eip = 0x28254c5b, esp = 0xbfbffbd4, ebp = 0xbfbffbf0 --- -- Paolo Italian FreeBSD User Group: http://www.gufi.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: More ULE bugs fixed.
As a side note/question: Is there any way to figure out which ULE version I'm running in a precompiled kernel? I just nuked my src tree by accident, and am not sure if i'm on 1.65 or something older.. If there is no way, is this perhaps an idea? Thanks, /Eirik Jeff Roberson wrote: On Fri, 17 Oct 2003, Bruce Evans wrote: How would one test if it was an improvement on the 4BSD scheduler? It is not even competitive in my simple tests. [scripts results deleted] Summary: SCHED_ULE was more than twice as slow as SCHED_4BSD for the obj and depend stages. These stages have little parallelism. SCHED_ULE was only 19% slower for the all stage. It apparently misses many oppurtunities to actually run useful processes. This may be related to /usr being nfs mounted. There is lots of idling waiting for nfs even in the SCHED_4BSD case. The system times are smaller for SCHED_ULE, but this might not be significant. E.g., zeroing pages can account for several percent of the system time in buildworld, but on unbalanced systems that have too much idle time most page zero gets done in idle time and doesn't show up in the system time. At one point ULE was at least as fast as 4BSD and in most cases faster. This is a regression. I'll sort it out soon. Test 1 for fair scheduling related to niceness: for i in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 do nice -$i sh -c "while :; do echo -n;done" & done top -o time [Output deleted]. This shows only a vague correlation between niceness and runtime for SCHED_ULE. However, top -o cpu shows a strong correlation between %CPU and niceness. Apparently, %CPU is very innacurate and/or not enough history is kept for long-term scheduling to be fair. Test 5 for fair scheduling related to niceness: for i in -20 -16 -12 -8 -4 0 4 8 12 16 20 do nice -$i sh -c "while :; do echo -n;done" & done time top -o cpu With SCHED_ULE, this now hangs the system, but it worked yesterday. Today it doesn't get as far as running top and it stops the nfs server responding. To unhang the system and see what the above does, run a shell at rtprio 0 and start top before the above, and use top to kill processes (I normally use "killall sh" to kill all the shells generated by tests 1-5, but killall doesn't work if it is on nfs when the nfs server is not responding). 661 root 112 -20 900K 608K RUN 0:24 27.80% 27.64% sh 662 root 114 -16 900K 608K RUN 0:19 12.43% 12.35% sh 663 root 114 -12 900K 608K RUN 0:15 10.66% 10.60% sh 664 root 114 -8 900K 608K RUN 0:11 9.38% 9.33% sh 665 root 115 -4 900K 608K RUN 0:10 7.91% 7.86% sh 666 root 1150 900K 608K RUN 0:07 6.83% 6.79% sh 667 root 1154 900K 608K RUN 0:06 5.01% 4.98% sh 668 root 1158 900K 608K RUN 0:04 3.83% 3.81% sh 669 root 115 12 900K 608K RUN 0:02 2.21% 2.20% sh 670 root 115 16 900K 608K RUN 0:01 0.93% 0.93% sh I think you cvsup'd at a bad time. I fixed a bug that would have caused the system to lock up in this case late last night. On my system it freezes for a few seconds and then returns. I can stop that by turning down the interactivity threshold. Thanks, Jeff Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current 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]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
binaries installed mult. times / no symlinks ?
Hi, I had been going through /usr/bin to see what I would need for a very small installation and noticed that there are binaries installed multiple times with different names of course. My question now would be if symlinking wouldn't suffice ? From those that I had not deleted I remember the following duplicates that most likely are not all of those exist... Mail -> mail Mail -> mailx less -> more awk -> nawk nvi -> nview cksum -> sum reset -> tset nvi -> vi nvi -> view -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[current tinderbox] failure on i386/pc98
TB --- 2003-10-19 07:49:42 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-10-19 07:49:42 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-10-19 07:49:42 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-10-19 07:55:55 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: populating >>> /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything.. TB --- 2003-10-19 08:52:09 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Oct 19 08:52:09 GMT 2003 [...] /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/ep/if_ep.c:967: warning: passing arg 1 of `bus_space_write_2' from incompatible pointer type /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/ep/if_ep.c:967: warning: passing arg 2 of `bus_space_write_2' from incompatible pointer type /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/ep/if_ep.c:968: warning: passing arg 1 of `bus_space_write_2' from incompatible pointer type /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/ep/if_ep.c:968: warning: passing arg 2 of `bus_space_write_2' from incompatible pointer type /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/ep/if_ep.c:969: warning: passing arg 1 of `bus_space_write_2' from incompatible pointer type /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/ep/if_ep.c:969: warning: passing arg 2 of `bus_space_write_2' from incompatible pointer type /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/ep/if_ep.c:970: warning: passing arg 1 of `bus_space_write_2' from incompatible pointer type /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/ep/if_ep.c:970: warning: passing arg 2 of `bus_space_write_2' from incompatible pointer type *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. TB --- 2003-10-19 08:54:59 - TB --- /usr/bin/make returned exit code 1 TB --- 2003-10-19 08:54:59 - TB --- ERROR: failed to build generic kernel TB --- 2003-10-19 08:54:59 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB Keyboard questions
Hi I have been trying to install FreeBSD 5.1 with a Logitech USB keyboard. But I have been unable to do that since it looks like FreeBSD 5.1 doesnt recognize the keyboard when it hasnt loaded the kernel. I then tried to install FreeBSD 4.8 and it worked like a charm with the USB keyboard. My first question is; Why isnt there support for a USB Keyboard during the installation of FreeBSD 5.1 and during the boot up process as well? I am unable to use it in the boot screen of FreeBSD 5.1. My second question is; I have been able to get the usb keyboard working in FreeBSD after help in the question mailing list, but when I use it I tend to every now and then get the same character again, this happens most often when im typing fast. I gues this is common knowledg but since Im new in current and new to using USB Keyboard in FreeBSD and I havent found much searching in Google. Is there a way to stop it or is it a bug in the USB source for FreeBSD, or just me. Mostly intrested in the status of this. Im running FreeBSD 5.1 release #0 with Generic kernel. Motherboard: Abit KD7 CPU: AMD Baraton Keyboard: Logitech cordless comfort With regards Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[current tinderbox] failure on i386/i386
TB --- 2003-10-19 06:27:41 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-10-19 06:27:41 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-10-19 06:27:41 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-10-19 06:30:24 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: populating >>> /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything.. TB --- 2003-10-19 07:30:18 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Oct 19 07:30:18 GMT 2003 >>> Kernel build for GENERIC completed on Sun Oct 19 07:44:30 GMT 2003 TB --- 2003-10-19 07:44:30 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- /usr/bin/make -B LINT TB --- 2003-10-19 07:44:30 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Oct 19 07:44:30 GMT 2003 [...] cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror -finstrument-functions -Wno-inline /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev/ep/if_ep.c cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror -finstrument-functions -Wno-inline /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev/ep/if_ep_eisa.c cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror -finstrument-functions -Wno-inline /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev/ep/if_ep_isa.c cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -DGPROF -falign-function
acpi on fujitsu-siemens
Hi! Is there way to make acpi work on fujitsu-siemens (amd 2500+)? I have tried to search google, but no go. dmesg and sysctl outputs are below. acpiconf -s 1 or 2 doesn't work. I guess because those errors. Have someone made it work on fujitsu-siemens? I would be grateful for any help you can give me. And is there any new patches for acpi, or something? Using FreeBSD - current. There was no luck either 4.8. dmesg output: Preloaded elf module "/boot/kernel/acpi.ko" at 0xc098821c. acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.LNKU._CRS] (Node 0xc40e49c0), AE_AML_UNINITIALIZED_LOCAL ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.LNKU._CRS] (Node 0xc40e49c0), AE_AML_UNINITIALIZED_LOCAL acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_cpu0: port 0x530-0x537 on acpi0 acpi_tz0: port 0x530-0x537 on acpi0 acpi_tz0: _CRT value is absurd, ignored (205.0C) acpi_tz0: _PSV value is absurd, ignored (200.0C) acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.LNKU._CRS] (Node 0xc40e49c0), AE_AML_UNINITIALIZED_LOCAL ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.LNKU._CRS] (Node 0xc40e49c0), AE_AML_UNINITIALIZED_LOCAL pci0: on pcib0 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.LNKU._CRS] (Node 0xc40e49c0), AE_AML_UNINITIALIZED_LOCAL ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.LNKU._CRS] (Node 0xc40e49c0), AE_AML_UNINITIALIZED_LOCAL pcib1: at device 1.0 on pci0 pci1: on pcib1 atkbdc0: port 0x64,0x60 irq 1 on acpi0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 0 on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 acpi_ec0: port 0x66,0x62 on acpi0 ACPI-0438: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.BAT1._STA] (Node 0xc4171e00), AE_NO_HARDWARE_RESPONSE ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.BAT1._STA] (Node 0xc4171e00), AE_NO_HARDWARE_RESPONSE acpi_cmbat0: on acpi0 acpi_acad0: on acpi0 ACPI-0438: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.BAT1._BST] (Node 0xc4171dc0), AE_NO_HARDWARE_RESPONSE :acpi_sysctl: acpicmbat 1 1K 1K1 16 acpisem19 3K 3K 19 64,128 acpitask 0 0K 1K4 16,32 acpica 132473K 73K12187 16,32,64,128,256,512,1024,2048 acpibatt 1 1K 1K1 16 acpidev57 1K 1K 57 16,32 debug.acpi.acpi_ca_version: 0x20030619 debug.acpi.semaphore_debug: 0 hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 5 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 hw.acpi.disable_on_poweroff: 1 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3332 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: -1 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: -1 hw.acpi.thermal.tz0._ACx: 3432 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 59 hw.acpi.battery.time: -1 hw.acpi.battery.state: 1 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 0 machdep.acpi_timer_freq: 3579545 machdep.acpi_root: 1013648 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
