lib broken
On today's build, got the following: cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -DLIBC_MAJOR=5 -D__DBINTERFACE_PRIVATE -DINET6 -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -DYP -DHESIOD -c /usr/src/lib/libc/../libc/stdlib/strfmon.c -o strfmon.o /usr/src/lib/libc/../libc/stdlib/strfmon.c: In function `strfmon': /usr/src/lib/libc/../libc/stdlib/strfmon.c:302: syntax error before `else' /usr/src/lib/libc/../libc/stdlib/strfmon.c:233: label `end_error' used but not defined /usr/src/lib/libc/../libc/stdlib/strfmon.c:162: label `format_error' used but not defined /usr/src/lib/libc/../libc/stdlib/strfmon.c:144: label `e2big_error' used but not defined cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 Stop in /usr/src/lib/libc. from strfmon.c: $FreeBSD: src/lib/libc/stdlib/strfmon.c,v 1.1 2001/09/05 18:50:02 phantom Exp $ Beech -- Micro$oft: Where can we make you go today? --- Beech Rintoul - IT Manager - Instructor - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Anchorage Gospel Rescue Mission \ / - NO HTML/RTF in e-mail | P.O. Box 230510 X - NO Word docs in e-mail | Anchorage, AK 99523-0510 / \ - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: unpleasant ps output and possible related problems.
On Wed, Sep 05, 2001 at 11:21:06PM -0400, Mike Barcroft wrote: I think it can safely be said that you're rebooting too much. The process can be simplified to: make world make kernel mergemaster reboot For -current I would suggest a slight modification to this -- to make sure everything compiles before installing any bits: make buildworld make buildkernel make installkernel make installworld mergemaster reboot reboot between the installkernel and installworld steps if you like. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: linux netscape hangs in -current
At Wed, 5 Sep 2001 15:50:31 -0700, Steve Kargl wrote: Linux netscape appears to be having problems with the kernel's linux compatibility module. troutmask:kargl[202] uname -a FreeBSD troutmask.apl.washington.edu 5.0-CURRENT FreeBSD 5.0-CURRENT\ #0: Fri Jul 27 16:04:55 PDT 2001 World built on 27 Jul 01. troutmask:kargl[203] ps | grep comm 82408 v0 R 4:37.11 /usr/local/lib/netscape-linux/communicator-linux-4.77 82413 v0 I 0:00.20 (dns helper) (communicator-lin) troutmask:kargl[204] truss -p 82408 gettimeofday(0x500b012c,0x0) = 2 (0x2) linux_sigreturn(0x500b01ac) = 1 (0x1) SIGNAL 14 SIGNAL 14 gettimeofday(0x500b012c,0x0) = 2 (0x2) linux_sigreturn(0x500b01ac) = 1 (0x1) SIGNAL 14 SIGNAL 14 ad nausem ^C I'm seeing the same with linux netscape 4.78 on a August 6th -current. Netscape starts hanging as soon as I try to load something complicated, e.g. animated gifs, JAVA applet, etc., and I have to kill -9 the process. It seems I can avoid the hang by running netscape -synchronous instead of just netscape. I had learned about the -synchronous flag when I ran into trouble with FreeBSD-netscape / XFree86-4 a while ago: Without the -synchronous flag I would very soon get loads of error popups saying Xlib: unexpected async reply or some such. It seems -synchronous is becoming a magic spell for netscape. -- Regards, Georg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
error using make world
Hi I just updated my source tree from a fresh install then i tried to make world and got the following error: sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 config /usr/obj/usr/src/i386/usr/sbin cd /usr/src/usr.sbin/kbdcontrol; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/usr.sbin/kbdcontrol created for /usr/src/usr.sbin/kbdcontrol lex -t /usr/src/usr.sbin/kbdcontrol/lex.l lex.c rm -f .depend mkdep -f .depend -a-I/usr/src/usr.sbin/kbdcontrol -I/usr/obj/usr/src/i386/usr/include /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c lex.c cd /usr/src/usr.sbin/kbdcontrol; make _EXTRADEPEND echo kbdcontrol: /usr/obj/usr/src/i386/usr/lib/libc.a /usr/obj/usr/src/i386/usr/lib/libl.a .depend cc -O -pipe -I/usr/src/usr.sbin/kbdcontrol -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c *** Error code 1 Stop in /usr/src/usr.sbin/kbdcontrol. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I am not sure if I should have posted it here if I shouldn't have, then where should I ?? Is there something i forgot or should have known?? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lib broken
Known issue. The problematic file has been temporarily unconnected from build. On Thu, Sep 06, 2001 at 12:16:01AM -0800, Beech Rintoul wrote: On today's build, got the following: cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -DLIBC_MAJOR=5 -D__DBINTERFACE_PRIVATE -DINET6 -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -DYP -DHESIOD -c /usr/src/lib/libc/../libc/stdlib/strfmon.c -o strfmon.o /usr/src/lib/libc/../libc/stdlib/strfmon.c: In function `strfmon': /usr/src/lib/libc/../libc/stdlib/strfmon.c:302: syntax error before `else' /usr/src/lib/libc/../libc/stdlib/strfmon.c:233: label `end_error' used but not defined /usr/src/lib/libc/../libc/stdlib/strfmon.c:162: label `format_error' used but not defined /usr/src/lib/libc/../libc/stdlib/strfmon.c:144: label `e2big_error' used but not defined cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 Stop in /usr/src/lib/libc. from strfmon.c: $FreeBSD: src/lib/libc/stdlib/strfmon.c,v 1.1 2001/09/05 18:50:02 phantom Exp $ -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Are you guys on crack? Scheme is just a dialect of LISP, where LISP could also just as easily be any one of MacLisp, InterLisp, Franz Lisp, Common Lisp or one of many other possibilities. The very acronym lacks specific meaning without an additional qualifier. Scheme can also dynamically build and evaluate data as code just as well as any other LISP dialect. Somebody needs to go back and take a CS class or something. :-) - Jordan From: Jim Bryant [EMAIL PROTECTED] Subject: Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS Date: Thu, 06 Sep 2001 00:58:25 -0500 FreeBSD Fanatic wrote: Show us a suitable LISP interpreter, then. $ cd ~/lang/Scheme/tinyscm-1.27 $ size scheme textdata bss dec hex filename 6134244763480 69298 10eb2 scheme Is that statically-linked? I'm curious to know the size of the bootloader forth footprint. The loader is about 150k, so I'm sure you could probably fit a nice Scheme interpreter in under that size... ?? Tinyscheme is a mostly complete R5RS Scheme (R5RS is the You can also conditionally-compile the components to make a smaller footprint. I'm highly in favor of Scheme replacing 4th... It's a very easy language to learn (only 11 special forms) yet still powerful (you can't pass code as data in BASIC ;). If you replace the boot loader interpreter, pick Scheme over LISP. There are lots of implementations: siod, scm, mit-scheme, MzScheme, and tinyscheme are among the better ones. --Rick C. Petty, aka Snoopy [EMAIL PROTECTED] I still think that Scheme has far less proficient programmers than LISP. BTW: In LISP, *EVERYTHING* is data. LISP was executing data as code and writing self-replicating programs around 1951 or 1952. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Jordan Hubbard wrote: Are you guys on crack? Scheme is just a dialect of LISP, where LISP could also just as easily be any one of MacLisp, InterLisp, Franz Lisp, Common Lisp or one of many other possibilities. The very acronym lacks specific meaning without an additional qualifier. Scheme can also dynamically build and evaluate data as code just as well as any other LISP dialect. Somebody needs to go back and take a CS class or something. :-) - Jordan oops... mea culpa! not nuff caffine, i got my languages mixed there... jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! POWER TO THE PEOPLE! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
On Thu, Sep 06, 2001 at 12:43:59PM +0900, Katsushi Kobayashi wrote: I believe the name iLink is not popular in outside of Japan. AFAIK that is Sony's name for it. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI and PS/2 mouse problem
As reported in this list by several people, you may be seeing that your PS/2 mouse is not detected after the recent ACPI update. This seems to be caused by ACPI in some BIOS assigns IRQ 12 (mouse interrupt) to both the PS/2 mouse device node and the system reserved resource node. To see if this is to be your case, put the following line in /boot/device.hints and reboot. debug.acpi.disable=sysresource If this brings your mouse back, I recommend you to keep that line there until the proper fix is committed. If it doesn't solve the problem, there must be other causes ;-( You had better contact the FreeBSD ACPI developers ([EMAIL PROTECTED]) ML. Kazu PS: I am going to commit some update to the psm driver shortly. But, that alone won't fix the problem. Sorry... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3CXFE575CT-JP with NEWCARD doesn't work
On Wed, Sep 05, 2001 at 11:51:07AM -0400, Jonathan Chen wrote: A complete dmesg from a verbose boot with both the successful and failed attempts would be a good start. It would also be useful to know what card you're using. The card is a Lucent wavelan. I haven't tried this with another card though, let me know if that might me usefull. Find attached the two dmesgs. They are both build after a cvsup. For one of the two kernels I have replaced src/sys/pccard/ with the one from August 20. I have also included my kernel config. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM machine i386 cpu I686_CPU ident MYNEW maxusers32 options INET#InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options MD_ROOT #MD is a potential root device options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE#Allow users to grab the console options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV# install a CDEV entry in /dev device isa device pci device fdc device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering device atkbdc 1 device atkbd device psm device vga device sc 1 device npx device apm device pmtimer device card device pcic device sio device wi device random # Entropy device device loop# Network loopback device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory disks device bpf # Berkeley packet filter device uhci device usb # USB Bus (required) device ugen# Generic options PSEUDOFS options COMPAT_LINUX options LINPROCFS options DDB options INCLUDE_CONFIG_FILE options IPFIREWALL options IPDIVERT Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #10: Thu Sep 6 09:41:15 CEST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP Calibrating clock(s) ... TSC clock: 299933216 Hz, i8254 clock: 1193150 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Pentium II Xeon/Celeron (299.94-MHz 686-class CPU) Origin = GenuineIntel Id = 0x66a Stepping = 10 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 134086656 (130944K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0032c000 - 0x07fd7fff, 130727936 bytes (31916 pages) avail memory = 127447040 (124460K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f0220 bios32: Entry = 0xfc465 (c00fc465) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xedcd pnpbios: Found PnP BIOS data at 0xc00f8ed0 pnpbios: Entry = f:9344 Rev = 1.0 pnpbios: Event flag at 510 pnpbios: OEM ID 1934f351 Other BIOS signatures found: Preloaded elf kernel kernel at 0xc0306000. null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71948086) Using $PIR table, 7 entries at 0xc00f0190 apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443MX host to PCI bridge at pcibus 0 on motherboard pci0: physical bus=0 found- vendor=0x8086, dev=0x7194, revid=0x01 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 map[10]: type 1, range 32, base ff40, size 22, enabled map[14]: type 1, range 32,
Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/modules/ccd Makefilesrc/sys/sys ccdvar.h
On Wed, 5 Sep 2001, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], David O'Brien writes: Use DEVFS and it will work. Then it needs to be backed out. This is the first thing that does not work w/NODEVFS and I don't believe the Project has agreed that absolutly requiring DEVFS is OK at this time. No, in fact, clearcut warnings has been sent for over half a year that after july 1st 2001 !DEVFS compatibility were no longer a requirement and that DEVFS should be considered mandatory. This was decreed but not agreed to. I don't use devfs and don't plan to use it until it works at least as well as specfs (if this is possible). I have noticed about 10 minor bugs in it despite only running it to test it every 6 months or so. Examples: - file time updates are broken in several ways. - stat() doesn't work right on devfs directories (st_size and st_blocks zero for all devfs files, but should be nonzero for directories). - pathconf() doesn't work right on devfs directrories (_PC_NAME_MAX and _PC_PATH_MAX are unsupported, but must be supported for directories). - acd devices still have insecure modes (world readable). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/modules/ccd Makefile src/sys/sys ccdvar.h
In message [EMAIL PROTECTED], Bruce Evans writes: This was decreed but not agreed to. I don't use devfs and don't plan to use it until it works at least as well as specfs (if this is possible). I have noticed about 10 minor bugs in it despite only running it to test it every 6 months or so. Examples: Why don't you report such findings then ? - file time updates are broken in several ways. Details ? - stat() doesn't work right on devfs directories (st_size and st_blocks zero for all devfs files, but should be nonzero for directories). Where is this requirement from ? - pathconf() doesn't work right on devfs directrories (_PC_NAME_MAX and _PC_PATH_MAX are unsupported, but must be supported for directories). OK, that's a bug. - acd devices still have insecure modes (world readable). That is not a fault in DEVFS but in the driver. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
amd broken
This commit breaks the build of amd: obrien 2001/09/05 09:54:21 PDT Modified files: usr.sbin/amd Makefile.inc usr.sbin/amd/include newvers.sh Log: Try to determine the OS version and architecture for what is being built vs. the building machine. PR: 14040 Revision ChangesPath 1.8 +4 -1 src/usr.sbin/amd/Makefile.inc 1.4 +17 -10src/usr.sbin/amd/include/newvers.sh This is because of +if [ -e ../../../sys/conf/newvers.sh ]; then in newvers.sh It happens to work if I build amd in /usr/src. If I have /usr/obj/... the Makefile is executed in the object directory, so that the path is wrong. The 'else' part of the above fails to generate the HOST_OS_VERSION, and this makes the build to fail. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/modules/ccd Makefilesrc/sys/sys ccdvar.h
On Thu, 6 Sep 2001, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Bruce Evans writes: This was decreed but not agreed to. I don't use devfs and don't plan to use it until it works at least as well as specfs (if this is possible). I have noticed about 10 minor bugs in it despite only running it to test it every 6 months or so. Examples: Why don't you report such findings then ? As you know, I don't believe in devfs :-). - file time updates are broken in several ways. Details ? I actually did report a few of these to you in private mail. The main ones are: - updates done by getnanotime(), so they always have low resolution and are incoherent with time(1). Fix: use vfs_timestamp(). - missing access checking for VA_UTIMES_NULL. Fix: clone ufs_setattr() better. - missing atime updates for readdir(). - stat() doesn't work right on devfs directories (st_size and st_blocks zero for all devfs files, but should be nonzero for directories). Where is this requirement from ? POLA. It's strange and less than useful for utilities like ls(1) to show a zero size for directories... (st_size is unspecified for directories in POSIX). - acd devices still have insecure modes (world readable). That is not a fault in DEVFS but in the driver. There are some more strange modes, although maybe no more security-related ones, including some in devfs itself: Index: devfs_devs.c === RCS file: /home/ncvs/src/sys/fs/devfs/devfs_devs.c,v retrieving revision 1.15 diff -u -2 -r1.15 devfs_devs.c --- devfs_devs.c26 May 2001 08:27:52 - 1.15 +++ devfs_devs.c13 Aug 2001 07:43:23 - @@ -222,5 +223,5 @@ dd-de_dirent-d_type = DT_DIR; - dd-de_mode = 0755; + dd-de_mode = 0555; dd-de_links = 2; dd-de_dir = dd; @@ -338,5 +339,5 @@ de-de_uid = 0; de-de_gid = 0; - de-de_mode = 0666; + de-de_mode = 0755; de-de_dirent-d_type = DT_LNK; pdev = dev-si_parent; Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
In message [EMAIL PROTECTED] Jim Bryant writes: : I doubt if the bootloader will ever change from FORTH, but if it : does, I suggest LISP as the preferred choice on a short-list of : potential replacements. It would make it very cool junior kernel hacker task to use lisp in the boot loader... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
In message [EMAIL PROTECTED] Toshihiko ARAI-san writes: : By the way, alias of firewire was i.LINK and IEEE1394, but the FreeBSD : people selected it as firewire? FreeBSD hasn't selected a name, but lots of folks here call it firewire. I'd be strongly inclined to use the same name that NetBSD uses. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
In message [EMAIL PROTECTED] Mark Santcroos writes: : On Thu, Sep 06, 2001 at 12:43:59PM +0900, Katsushi Kobayashi wrote: : I believe the name iLink is not popular in outside of Japan. : : AFAIK that is Sony's name for it. IT is. Firewire is Apple's name. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [acpi-jp 1246] ACPI and PS/2 mouse problem
Thanks Yokota-san for tracking down the problem.
As reported in this list by several people, you may be seeing that
your PS/2 mouse is not detected after the recent ACPI update.
This seems to be caused by ACPI in some BIOS assigns IRQ 12 (mouse
interrupt) to both the PS/2 mouse device node and the system reserved
resource node.
And if such a problem was found, please send ACPI data with the
report. This is very useful info. for our debugging.
To get ACPI data,
# acpidump -o foo.dsdt foo.asl
and send both files to acpi-jp@. See also acpidump(8).
To see if this is to be your case, put the following line in
/boot/device.hints and reboot.
debug.acpi.disable=sysresource
I personally, don't have enough time to hack the code for now (sorry),
but I think that newly added `placeholders' code causes the problem
for my first impression.
for (i = 0; i 100; i++) {
rid = i;
res = bus_alloc_resource(dev, SYS_RES_IOPORT, rid, 0, ~0, 1, 0);
rid = i;
res = bus_alloc_resource(dev, SYS_RES_MEMORY, rid, 0, ~0, 1, 0);
rid = i;
res = bus_alloc_resource(dev, SYS_RES_IRQ, rid, 0, ~0, 1, 0);
}
Mike, do you have any idea on this?
Anyway, Yokota-san thank you very much for finding a workaround.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
In article local.mail.freebsd-current/[EMAIL PROTECTED] you write: In message [EMAIL PROTECTED] Jim Bryant writes: : I doubt if the bootloader will ever change from FORTH, but if it : does, I suggest LISP as the preferred choice on a short-list of : potential replacements. It would make it very cool junior kernel hacker task to use lisp in the boot loader... Hmm. Other cool tasks include: - substituting TAB for space in correct places and vice versa. - fixing incorrect code indentation. - wholesale removal of _P() prototypes. - rewriting all perl scripts in sh. - using Java instead of C in the kernel. All of the above will provide much needed features and functionality for the upcoming 5.0 release. They will dramatically raise the bar and provide a significant performance boost for the system. After all, it is well known(*) than LISP is already SMP capable, while Forth is single threaded, and it is critically important that the bootloader be SMP enabled. :-) Seriously now, don't we have better things to spend our time and energies on than re-implementing code that already works? -- Jonathan (*) 4 out of 5 handwavers agree on this point, according to the Journal of Irreproducible Results and Department of FUD. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
On Thu, Sep 06, 2001 at 09:55:17AM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] Mark Santcroos writes: : On Thu, Sep 06, 2001 at 12:43:59PM +0900, Katsushi Kobayashi wrote: : I believe the name iLink is not popular in outside of Japan. : : AFAIK that is Sony's name for it. IT is. Firewire is Apple's name. I believe that it is also an Apple trademark, that's why no one but Apple sells 1394 components under the Firewire name. Adopting the same name could get FreeBSD into trouble irregardless of who works there. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
$ size scheme textdata bss dec hex filename 6134244763480 69298 10eb2 scheme Is that statically-linked? I'm curious to know the size of the bootloader forth footprint. The loader is about 150k, so I'm sure you could probably fit a nice Scheme interpreter in under that size... ?? Dynamically linked. Here is the statically linked size: $ size scheme textdata bss dec hex filename 127659 110929236 147987 24213 scheme Note that this is misleading because in order to build a standalone binary you'd have to reduce libc dependence quite a bit. Basically avoid anything that makes a syscall. You can also throw out printf and friends, which will save you over 10KB! On the other side you'd have to add loader specific code (either in Scheme or in c). Here is the /boot/loader size for comparison sake: textdatabss dec hex 4096147456 0 151552 25000 Tinyscheme is a mostly complete R5RS Scheme (R5RS is the You can also conditionally-compile the components to make a smaller footprint. I'm highly in favor of Scheme replacing 4th... It's a very easy language to learn (only 11 special forms) yet still powerful (you can't pass code as data in BASIC ;). If you replace the boot loader interpreter, pick Scheme over LISP. There are lots of implementations: siod, scm, mit-scheme, MzScheme, and tinyscheme are among the better ones. Indeed. But ultimately someone has to do the actual work for this to go beyond mere wishful thinking. I'd be happy to help out (but not take on the whole task) if anyone braves the naysayers :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: amd broken
On Thu, Sep 06, 2001 at 04:58:28PM +0200, Harti Brandt wrote: It happens to work if I build amd in /usr/src. If I have /usr/obj/... You can guess how I tested it... ;-) My reference box's build failed last night in libc. I'm updating it now so I can fix this. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: corrupted 'w' output
[Moved to -current, BCC'd to -hackers] Eugene L. Vorokov [EMAIL PROTECTED] writes: Hello, I updated from -current yesterday, ran make world; make kernel KERNCONF=X and went to bed. When I rebooted with fresh kernel this morning, I noticed something strange: vel@bugz:/usr/src # w 3:47PM up 5:38, 4 users, load averages: 0.00, 0.11, 0.08 USER TTY FROM LOGIN@ IDLE WHAT vel p0 kg.infotecs.ru 10:11AM 2 ssh -l vel bsx.ru vel p1 kg.infotecs.ru 10:22AM - w vel p2 kg.infotecs.ru 12:13PM 1:55 \M-[\M-!\^D\b (tcsh) vel p3 kg.infotecs.ru 12:53PM 2 \M-[\M-!\^D\b (tcsh) This only happens for terminals that are in a shell, when something else is running, output isn't corrupted. I think someone reported similar problem with 'ps' output. Regards, Eugene Those shell argv[0]'s are generated by login(1). I wonder if it was a recent commit to src/usr.bin/login/login.c that is causing it. Can you try locally backing out Rev. 1.68 (and Rev 1.36 of Makefile)? You will ofcourse have to relogin to see whether the w(1) output has changed. BTW, I can't reproduce this problem locally. Is there any special about your local configuration, particularly regarding PAM? Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
+ [EMAIL PROTECTED], Warner Losh wrote: : By the way, alias of firewire was i.LINK and IEEE1394, but the FreeBSD : people selected it as firewire? FreeBSD hasn't selected a name, but lots of folks here call it firewire. I'd be strongly inclined to use the same name that NetBSD uses. Do you know the current situation of development by NetBSD? If development is separate, power has dispersed. It will become a loss for BSD. -- Toshihiko ARAI To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
On Thu, 6 Sep 2001, Jonathan Lemon wrote: It would make it very cool junior kernel hacker task to use lisp in the boot loader... Seriously now, don't we have better things to spend our time and energies on than re-implementing code that already works? But, if we rewrite the bootloader in LISP we can get RMS to maintain it! *duck* -- Never put off until tomorrow what you can do today. There might be a law against it by that time. -- /usr/games/fortune, 07/30/2001 Brandon D. Valentine bandix at looksharp.net To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Linuxulator: possible Giant pushdown victim
On 06-Sep-01 Marcel Moolenaar wrote: On Wed, Sep 05, 2001 at 02:47:28PM -0700, John Baldwin wrote: Yes, you can trace indiviudal processes though, using 'trace pid', and I'm more curious about the traces of the Mozilla processes. Ok, here it is: db ps pid proc addruid ppid pgrp flag stat wmesg wchan cmd 520 cd193ee0 cd256000 4152 517 514 02 2 mozilla-bin 519 cd197840 cd1ab000 4152 517 514 202 3 pause c17d3000 mozilla-bin 518 cd193880 cd27 4152 517 514 02 3 select c039bb24 mozilla-bin 517 cd193aa0 cd27b000 4152 514 514 02 2 mozilla-bin 514 cd194100 cd244000 4152 505 514 004002 2 mozilla-bin ... Note that 3 of these are runnable (stat of 2 == SRUN). In top, see if they are chewing up lots of time. db trace 514 mi_switch(cd194100) at mi_switch+0x1a0 userret(cd194100,cd245fa8,c5,a,bfbfeae0) at userret+0x395 syscall(2f,2f,2f,282397c0,bfbfeae0) at syscall+0x3c9 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (148, Linux ELF, linux_fdatasync), eip = 0x285c2074, esp = 0xbfbfeac8, ebp = 0xbfbfeb98 --- It was returning from a syscall but had to do a context switch due to PS_NEEDRESCHED because it got preempted. db trace 517 mi_switch(0,cd193aa0,811f874,cd27cfa0,c02bead6) at mi_switch+0x1a0 _mtx_unlock_sleep(c039e860,0,c030b460,497) at _mtx_unlock_sleep+0x204 syscall(2f,2f,2f,811f874,1) at syscall+0x48a syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (514), eip = 0x285a31a7, esp = 0x811f858, ebp = 0x811f9b4 --- Weird syscall number (514). This one was blocked on a mutex that was just released. I'm betting that 0xc039e860 is Giant? Perhaps not though? db trace 518 mi_switch(cd19399c,cd193880,0,2,0) at mi_switch+0x1a0 cv_timedwait_sig(c039bb24,cd19399c,dad,1,bfbffeb8) at cv_timedwait_sig+0x65b poll(cd193880,cd271f44,cd19399c,cd193880,bf3ffa4c) at poll+0x656 linux_poll(cd193880,cd271f80,bf3ffa4c,88b8,bf3ffa4c) at linux_poll+0x11f syscall(2f,2f,2f,bf3ffa4c,88b8) at syscall+0x339 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (168, Linux ELF, linux_poll), eip = 0x285c7894, esp = 0xbf3ff9e8, ebp = 0xbf3ff9f4 --- Asleep in select as ps shows. db trace 519 mi_switch(cd19795c,cd197840,c17d3000,c02f3a60,2) at mi_switch+0x1a0 msleep(c17d3000,cd19795c,168,c02f0f49,0) at msleep+0x71a sigsuspend(cd197840,cd1acf4c,cd1acf44,bfbffeb8,cd19795c) at sigsuspend+0x19f linux_rt_sigsuspend(cd197840,cd1acf80,bf1ff94c,bf1ff94c,28239fc8) at linux_rt_sigsuspend+0x8e syscall(2f,2f,2f,28239fc8,bf1ff94c) at syscall+0x339 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (179, Linux ELF, linux_rt_sigsuspend), eip = 0x2851c656, esp = 0xbf1ff92c, ebp = 0xbf1ff934 --- Asleep in pause as ps shows. db trace 520 mi_switch(cd193ee0) at mi_switch+0x1a0 userret(cd193ee0,cd257fa8,0,208,befffc00) at userret+0x395 syscall(2f,2f,2f,befffd24,befffc00) at syscall+0x3c9 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (0, Linux ELF, nosys), eip = 0x285b8bd4, esp = 0xbefffb24, ebp = 0xbefffbf4 --- Another instance of being preempted upon return to userland. Possible that the regs in the trapframe are altered to hold return values and thus that the syscall number is invalid. Hmm. What locks do all these processes hold? I would expect the ones in stat 3 (SSLEEP) to hold none, but the others might hold locks. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Firewire driver available
In message [EMAIL PROTECTED] Toshihiko ARAI writes: : : By the way, alias of firewire was i.LINK and IEEE1394, but the FreeBSD : : people selected it as firewire? : : FreeBSD hasn't selected a name, but lots of folks here call it : firewire. I'd be strongly inclined to use the same name that NetBSD : uses. : : Do you know the current situation of development by NetBSD? : If development is separate, power has dispersed. It will become a : loss for BSD. I do not have a laptop running NetBSD that has a ieee1394 device on it. However, looking at their sys/dev/ieee1394, it appears that they have a fairly complete setup. I don't know if it works or not, but it is there for anyone to see. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
postfix fails to start
Hmm .. thought i should update my current machine 2 hours ago, cvs´d a tree, made and installed it. Reboot. Got: Sep 6 21:33:48 bert postfix[15838]: fatal: could not find any active network interfaces With the previous binary, a 4.3 CD binary, a then newly compiled postfix and postfix-current (both freshly cvs updated). Reinstalled the previous current from Aug, 14 and postfix ran fine again. Needless to say that the joy was great :-( hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: error using make world
On Thu, Sep 06, 2001 at 04:05:16PM +0200, Nick Martens wrote: I just updated my source tree from a fresh install then i tried to make world and got the following error: sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 config /usr/obj/usr/src/i386/usr/sbin cd /usr/src/usr.sbin/kbdcontrol; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/usr.sbin/kbdcontrol created for /usr/src/usr.sbin/kbdcontrol lex -t /usr/src/usr.sbin/kbdcontrol/lex.l lex.c rm -f .depend mkdep -f .depend -a-I/usr/src/usr.sbin/kbdcontrol -I/usr/obj/usr/src/i386/usr/include /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c lex.c cd /usr/src/usr.sbin/kbdcontrol; make _EXTRADEPEND echo kbdcontrol: /usr/obj/usr/src/i386/usr/lib/libc.a /usr/obj/usr/src/i386/usr/lib/libl.a .depend cc -O -pipe -I/usr/src/usr.sbin/kbdcontrol -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c *** Error code 1 I can't see the error here. If you're running make -j, don't do that because it hides the real error somewhere further back in the make output. Kris PGP signature
Re: postfix fails to start
From: Hellmuth Michaelis [EMAIL PROTECTED] Subject: postfix fails to start Date: Thu, Sep 06, 2001 at 09:46:15PM +0200 Hmm .. thought i should update my current machine 2 hours ago, cvs´d a tree, made and installed it. Reboot. Got: Sep 6 21:33:48 bert postfix[15838]: fatal: could not find any active network interfaces ifconfig output please ? -giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: postfix fails to start
On Thu, 6 Sep 2001 21:46:15 +0200 (METDST), [EMAIL PROTECTED] (Hellmuth Michaelis) said: Sep 6 21:33:48 bert postfix[15838]: fatal: could not find any active network interfaces I'm having a similar experience here. -- Michael D. Harnois bilocational bivocational Pastor, Redeemer Lutheran ChurchWashburn, Iowa 1L, UST School of Law Minneapolis, Minnesota Everyone thinks of changing the world, but no one thinks of changing himself. -- Leo Nikolaevich Tolstoy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: postfix fails to start
On Fri, 7 Sep 2001 03:49:38 +0300, Giorgos Keramidas [EMAIL PROTECTED] said: ifconfig output please ? On the bad kernel, an ifconfig shows that the network card for my outside interface has an ipaddr of 0.0.0.0. When I try to run dhclient manually on the interface it says dc0: not found. Going back to a kernel from a couple of days ago (in my case, from 4 September at 1925) solves the problem. -- Michael D. Harnois bilocational bivocational Pastor, Redeemer Lutheran ChurchWashburn, Iowa 1L, UST School of Law Minneapolis, Minnesota He who will not reason is a bigot; he who cannot is a fool; and he who dares not, is a slave. -- William Drummond To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
__getcwd errno 20 (Not a directory) vfs_cache.c
Hi,
I'm in the middle of trying to debug a java problem
and have found something I don't quite understand.
Basically, __getcwd() is returning errno 20, Not
a directory. man getcwd doesn't list ENOTDIR so I
started looking in the sources and found kern/vfs_cache.c:
if (vp-v_dd-v_id != vp-v_ddid) {
numcwdfail1++;
free(buf, M_TEMP);
return (ENOTDIR);
}
Could someone who is more familiar with the vfs
layers provide some pointers as to what is being
done here? The code is instrumented, and sysctl
has the following to say:
% sysctl -a | grep cwd
vfs.cache.numcwdcalls: 225014
vfs.cache.numcwdfail1: 845 1 - ENOTDIR
vfs.cache.numcwdfail2: 6775 2 - ENOENT
vfs.cache.numcwdfail3: 0
vfs.cache.numcwdfail4: 0
vfs.cache.numcwdfound: 217394
The really annoying aspect to this is that it doesn't
happen everytime, and happens more often when in a nfs
mounted directory vs. a local directory.
Thanks!
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
net-snmp port on -CURRENT?
Hi... I am trying to build net-snmp port on -CURRENT but don't have enough luck with it. Here's the error message on my system: -- cc -DINET6 -O -pipe -march=pentiumpro -Dfreebsd5 -I. -I../.. -I. -I./../.. -I./../../snmplib -I./.. -I.. -c host/hr_storage.c -fPIC -DPIC -o host/.libs/hr_storage.lo host/hr_storage.c: In function `var_hrstore': host/hr_storage.c:526: structure has no member named `m_mbufs' host/hr_storage.c:565: structure has no member named `m_clusters' host/hr_storage.c:565: structure has no member named `m_clfree' *** Error code 1 Stop in /usr/ports/net/net-snmp/work/ucd-snmp-4.2.1/agent/mibgroup. *** Error code 1 Stop in /usr/ports/net/net-snmp/work/ucd-snmp-4.2.1/agent. *** Error code 1 Stop in /usr/ports/net/net-snmp/work/ucd-snmp-4.2.1. *** Error code 1 Stop in /usr/ports/net/net-snmp. *** Error code 1 Stop in /usr/ports/net/net-snmp. *** Error code 1 Stop in /usr/ports/net/net-snmp. *** Error code 1 Stop in /usr/ports/net/net-snmp. -- /john Live Free OR Die To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: postfix fails to start
From the keyboard of Giorgos Keramidas: Hmm .. thought i should update my current machine 2 hours ago, cvs´d a tree, made and installed it. Reboot. Got: Sep 6 21:33:48 bert postfix[15838]: fatal: could not find any active network interfaces ifconfig output please ? Nothing has changed with the ifconfig output, the network ran fine, no troubles at all. Obviously postfix had trouble with _detecting_ one, which in turn seemed not to be postfix´ fault but -currents (an API changed ??) kernel (as said, after reinstalling the old kernel and modules but with the new userland postfix ran fine again). hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: __getcwd errno 20 (Not a directory) vfs_cache.c
You are not supposed to call __getcwd() directly.
Poul-Henning
In message [EMAIL PROTECTED], John W. De Boskey writes:
Hi,
I'm in the middle of trying to debug a java problem
and have found something I don't quite understand.
Basically, __getcwd() is returning errno 20, Not
a directory. man getcwd doesn't list ENOTDIR so I
started looking in the sources and found kern/vfs_cache.c:
if (vp-v_dd-v_id != vp-v_ddid) {
numcwdfail1++;
free(buf, M_TEMP);
return (ENOTDIR);
}
Could someone who is more familiar with the vfs
layers provide some pointers as to what is being
done here? The code is instrumented, and sysctl
has the following to say:
% sysctl -a | grep cwd
vfs.cache.numcwdcalls: 225014
vfs.cache.numcwdfail1: 845 1 - ENOTDIR
vfs.cache.numcwdfail2: 6775 2 - ENOENT
vfs.cache.numcwdfail3: 0
vfs.cache.numcwdfail4: 0
vfs.cache.numcwdfound: 217394
The really annoying aspect to this is that it doesn't
happen everytime, and happens more often when in a nfs
mounted directory vs. a local directory.
Thanks!
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: postfix fails to start
From the keyboard of Hellmuth Michaelis: From the keyboard of Giorgos Keramidas: Hmm .. thought i should update my current machine 2 hours ago, cvs´d a tree, made and installed it. Reboot. Got: Sep 6 21:33:48 bert postfix[15838]: fatal: could not find any active network interfaces ifconfig output please ? Nothing has changed with the ifconfig output, the network ran fine, Just reading Michael Harnois reply, it might be that the address was 0.0.0.0, the network ran with no trouble, i tried ifconfig and perhaps looked not detailed enough at it hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: RFC: hack volatile bzero and bcopy
On 07-Sep-01 Julian Elischer wrote: Here is a hack to remove the 20 or so warning messages from if_ie.c Most of them are due to the supply of volatile pointers to bcopy and bzero. I do the following to produce macros that call bzero and bcopy, but don't produce warning messages when called with volatile arguments. typedef void Xcopy( void volatile *, void volatile *, int); #define VBCOPY(A,B,L) (*(Xcopy *)bcopy)((A),(B),(L)) typedef void Xzero( void volatile *, int); #define VBZERO(A,L) (*(Xzero *)bzero)((A),(L)) sys/cdef.h already has some rather general purpose macros for thsi sort of thing in the form of __DEVOLATILE(), __DECONST(), and __DEQUALIFY(). -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: RFC: hack volatile bzero and bcopy
Actually I just discoverd that you can do: int function (volatile const *); (I guess you say you will not writ eto it, but that it may change of its own volition at times) anyhow setting this in bcopy would remove a heck of a lot of warnings in the kernel. On Thu, 6 Sep 2001, John Baldwin wrote: On 07-Sep-01 Julian Elischer wrote: Here is a hack to remove the 20 or so warning messages from if_ie.c Most of them are due to the supply of volatile pointers to bcopy and bzero. I do the following to produce macros that call bzero and bcopy, but don't produce warning messages when called with volatile arguments. typedef void Xcopy( void volatile *, void volatile *, int); #define VBCOPY(A,B,L) (*(Xcopy *)bcopy)((A),(B),(L)) typedef void Xzero( void volatile *, int); #define VBZERO(A,L) (*(Xzero *)bzero)((A),(L)) sys/cdef.h already has some rather general purpose macros for thsi sort of thing in the form of __DEVOLATILE(), __DECONST(), and __DEQUALIFY(). thanks, I'll go look at them. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI: HEADS UP (ACPI CA update)
I've just updated the ACPI CA components to the latest Intel release. You can read the release notes on Intel's website (http://developer.intel.com/technology/iapc/acpi). In addition, I've changed the default ACPI initialisation to the full, recommended-by-the-standard set of passes over the namespace. This has the potential to cause problems on some systems. If you are already using the debug.acpi.avoid sysctl, you will get the old behaviour (since the avoid mechanism does not affect some parts of the namespace initialisation). If the latest code locks up during device probes, try ok set debug.acpi.avoid= at the loader prompt. Outstanding issues: - The ACPI timecounter does not work on some ALi chipsets. - ACPI mode results in some PCI devices not being configured by the BIOS. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI: HEADS UP (ACPI CA update)
* Mike Smith [EMAIL PROTECTED] [010906 22:57] wrote: I've just updated the ACPI CA components to the latest Intel release. You can read the release notes on Intel's website (http://developer.intel.com/technology/iapc/acpi). In addition, I've changed the default ACPI initialisation to the full, recommended-by-the-standard set of passes over the namespace. This has the potential to cause problems on some systems. If you are already using the debug.acpi.avoid sysctl, you will get the old behaviour (since the avoid mechanism does not affect some parts of the namespace initialisation). If the latest code locks up during device probes, try ok set debug.acpi.avoid= at the loader prompt. Outstanding issues: - The ACPI timecounter does not work on some ALi chipsets. - ACPI mode results in some PCI devices not being configured by the BIOS. Any chance this will fix the problem with sound (pcm) that I mailed you about earlier? -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI: HEADS UP (ACPI CA update)
Outstanding issues: - The ACPI timecounter does not work on some ALi chipsets. - ACPI mode results in some PCI devices not being configured by the BIOS. Any chance this will fix the problem with sound (pcm) that I mailed you about earlier? I don't think so; I'm fairly sure this is the second issue listed above. I have a lot of PCI-related work that is sort-of-ready for integration which starts us down the path to fix this, but I need time to clean it up and test it, and I don't want to inflict *too* much misery on people all at once. It's also what I was working on the night I got hit... *shiver* To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems
Terry Lambert wrote: unknown: PNP0400 can't assign resources unknown: PNP0400 at port 0x378-0x37f on isa0 unknown: PNP0501 can't assign resources unknown: PNP0501 at port 0x3f8-0x3ff on isa0 unknown: PNP0501 can't assign resources unknown: PNP0501 at port 0x2f8-0x2ff on isa0 unknown: PNP0f13 can't assign resources unknown: PNP0f13 at irq 12 on isa0 unknown: PNP0303 can't assign resources unknown: PNP0303 at port 0x60 on isa0 unknown: PNP0800 failed to probe at port 0x61 on isa0 Known problem... see the -current archives. You are attaching twice: once because of ACPI, and again because of the hints. You need to comment the entries out of your hints file to make them not get attached twice. Actually not; You missed my comment that the DMESG was WITHOUT the ACPI module loaded; my real problem was a panic long before the serial probes. These pnp messages may be entries in hints twice? Apparently the AMD chipset is not served correctly by this ACPI code; I have this panic on one system and clock problems on another (Aladdin chipset; not that I love Acer) the clock runs almost exactly twice speed with the new ACPI; correctly without.) I saw a major acpi update come through this evening so I'm trying again... (that is, if strfmon and amd compile :-) -- Pete To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: net-snmp port on -CURRENT?
In article local.mail.freebsd-current/[EMAIL PROTECTED] you write: Hi... I am trying to build net-snmp port on -CURRENT but don't have enough luck with it. Here's the error message on my system: -- cc -DINET6 -O -pipe -march=pentiumpro -Dfreebsd5 -I. -I../.. -I. -I./../.. -I./../../snmplib -I./.. -I.. -c host/hr_storage.c -fPIC -DPIC -o host/.libs/hr_storage.lo host/hr_storage.c: In function `var_hrstore': host/hr_storage.c:526: structure has no member named `m_mbufs' host/hr_storage.c:565: structure has no member named `m_clusters' host/hr_storage.c:565: structure has no member named `m_clfree' *** Error code 1 The mbuf subsystem has been rewritten for -current, and mbuf statistics are handled differently now. The port will have to be updated to teach it about the new statistic layout. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems
Pete Carah wrote: Known problem... see the -current archives. It *is* a known problem. You are attaching twice: once because of ACPI, and again because of the hints. You need to comment the entries out of your hints file to make them not get attached twice. It's just not this one, since ACPI fails differently. Actually not; You missed my comment that the DMESG was WITHOUT the ACPI module loaded; my real problem was a panic long before the serial probes. These pnp messages may be entries in hints twice? No. They are PnP detected devices being detected twice. Since you posted this message to -current, I just assumed you had upgraded to the latest code, and thus were using ACPI (this is the same thing that ended up confusing Mike Smith, who also made the mistake in correcting me to say that ACPI was being loaded twice on your system). The general form of the problem is: 1) PnP BIOS tells FreeBSD about the devices 2) The device.hints tells FreeBSD about the devices See the -current list archives for details; look for Subject: of Re: unknown PNP hardware. Apparently the AMD chipset is not served correctly by this ACPI code; I have this panic on one system and clock problems on another (Aladdin chipset; not that I love Acer) the clock runs almost exactly twice speed with the new ACPI; correctly without.) I saw a major acpi update come through this evening so I'm trying again... (that is, if strfmon and amd compile :-) There is another known problem with ACER and ACPI timers, which is most properly fixed, as Mike pointed out, by the code checking to see if the timer is insane, and if it is, discarding it and not using it and going the old route instead. A quick hack, which was iscussed but not implemented at the time I read the message about it, would be to disable the ACPI timer (thinking about this, it should be possible to implement at boot time via sysctl to select the timer without the problem, but I have not tested this, and the timecounter code is rather opaque, in that it templates into hidden state containers which are not really globally accessible [made zero system call time functions hard, but not impossible, to write). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Now 2 ACPI strangeness, both AMD procs
K6-2-450, bus running at 95mhz, Acer 1541 (A? B?) All works fine with the new ACPI _except_ the clock; the time of day advances about twice as fast as it should, and I get LOTS of calcru negative time and time went backwards messages. We've seen this before; the Acer Aladdin X clocks are busted. Turn off the ACPI timer. A 'better' solution is going to be for us to sanity-check the ACPI timer and not use it when it's broken. I really need someone with one of these busted boards to spend a little time looking at the (really, really simple) code and experimenting to see what's going on. My athlon MB (ASUS A7V) still won't boot with the new ACPI, at all. Dies with a panic trying to attach something, saying can't allocate memory. The message disappears too fast to remember what it objected to; I think it was the fxp card. When the system panics, it *stops*. The message doesn't disappear at all. Please capture whatever is happening and write it down; this isn't a useful bug report. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Show us a suitable LISP interpreter, then. $ cd ~/lang/Scheme/tinyscm-1.27 $ size scheme textdata bss dec hex filename 6134244763480 69298 10eb2 scheme Is that statically-linked? I'm curious to know the size of the bootloader forth footprint. The loader is about 150k, so I'm sure you could probably fit a nice Scheme interpreter in under that size... ?? mass:/usr/obj/local0/build/src/sys/boot/ficlsize libficl.a textdata bss dec hex filename 1053968 04073 fe9 softcore.o (ex libficl.a) 296 0 0 296 128 sysdep.o (ex libficl.a) 20636 268 0 2090451a8 words.o (ex libficl.a) 4472 12 044841184 tools.o (ex libficl.a) 1684 0 01684 694 search.o (ex libficl.a) 856 0 0 856 358 math64.o (ex libficl.a) 2200 64 02264 8d8 vm.o (ex libficl.a) 2804 0 02804 af4 loader.o (ex libficl.a) 624 12 0 636 27c prefix.o (ex libficl.a) 840 0 0 840 348 stack.o (ex libficl.a) 2468 16 02484 9b4 ficl.o (ex libficl.a) 2620 0 02620 a3c dict.o (ex libficl.a) ie. almost all of the size is the dictionary/runtime library. It's quite hard to beat this, and to be frank, Scheme's syntax is not much better than Forth's. 8) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Now 2 ACPI strangeness, both AMD procs
On 06-Sep-01 Mike Smith wrote: K6-2-450, bus running at 95mhz, Acer 1541 (A? B?) All works fine with the new ACPI _except_ the clock; the time of day advances about twice as fast as it should, and I get LOTS of calcru negative time and time went backwards messages. We've seen this before; the Acer Aladdin X clocks are busted. Turn off the ACPI timer. A 'better' solution is going to be for us to sanity-check the ACPI timer and not use it when it's broken. I really need someone with one of these busted boards to spend a little time looking at the (really, really simple) code and experimenting to see what's going on. My athlon MB (ASUS A7V) still won't boot with the new ACPI, at all. Dies with a panic trying to attach something, saying can't allocate memory. The message disappears too fast to remember what it objected to; I think it was the fxp card. When the system panics, it *stops*. The message doesn't disappear at all. Please capture whatever is happening and write it down; this isn't a useful bug report. Unless you are on a 80x25 console with a fatal kernel trap and the new console testing code, in which case you may very well lose relevant portions of the panic messages. :-P Also, if his box is resetting after panic'ing it might be too fast. Serial consoles are an excellenet remedy for both of these problems. [ Not directly to you Mike, you know all of this already. ] -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [acpi-jp 1247] Re: ACPI and PS/2 mouse problem
I personally, don't have enough time to hack the code for now (sorry),
but I think that newly added `placeholders' code causes the problem
for my first impression.
Yes; this is something that I'm not happy about. It looks like these
resources are being badly abused by vendors as hints for allocation of
fresh resources, rather than truly reflecting the system configuration.
for (i = 0; i 100; i++) {
rid = i;
res = bus_alloc_resource(dev, SYS_RES_IOPORT, rid, 0, ~0, 1, 0);
rid = i;
res = bus_alloc_resource(dev, SYS_RES_MEMORY, rid, 0, ~0, 1, 0);
rid = i;
res = bus_alloc_resource(dev, SYS_RES_IRQ, rid, 0, ~0, 1, 0);
}
Mike, do you have any idea on this?
I'm not sure exactly what to do here. These resources contain information
we need to know about where we cannot put PnP devices. But if we feed the
information into our current resource manager, we end up with conflicts
with existing devices.
For the moment, I've changed the code to allocate IRQs shared. The
PS/2 mouse driver should do the same. I'm still trying to work out
what we can and cannot depend on here. 8(
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
RFC: hack volatile bzero and bcopy
Here is a hack to remove the 20 or so warning messages from if_ie.c
Most of them are due to the supply of volatile pointers to bcopy and
bzero.
I do the following to produce macros that call bzero and bcopy, but
don't produce
warning messages when called with volatile arguments.
typedef void Xcopy( void volatile *, void volatile *, int);
#define VBCOPY(A,B,L) (*(Xcopy *)bcopy)((A),(B),(L))
typedef void Xzero( void volatile *, int);
#define VBZERO(A,L) (*(Xzero *)bzero)((A),(L))
This is kind-of a hack but a couple of things come to mind:
1/ Most drivers should probably use volatile mor ethan they do if they
share
structures with hardware. These often need bcopy(), so this is probably
not an unlikely
combination..
2/ initializing these volatile structures with bzero is also not
unlikely.
3/ It probably wouldn't hurt if bzero ALWAYS had a volatile pointer
argument.
and it may remove several warnings in other drivers as well.
questions:
Is this hack to horrible to contemplate?
Is it a reasonable thing thing to define bzero to take a volatile
argument.
(It does not hurt to pass a nonvolatile argument to a volatile but the
reverse
produces an error message). I've compiled LINT with this change and it
compiles fine.
Should we define an official volatile_bcopy() to use in these cases,
even if it is just a (nicer) version of this hack in systm.h?
BTW what is ovbcopy() for? is it for overlaping?
I can't find a definition for it here, but google finds references in
true64.
(overlapping)
I notice that KAME ar the major users of it, and it's defined to be the
same as
bcopy..
I also notice that NetBSD are (or were) having a kill
ovbcopy/bcopy/bzero effort
to replace them with memcpy and friends.
--- if_ie.c Thu Sep 6 17:05:12 2001
+++ if_ie.c.new Thu Sep 6 17:03:42 2001
@@ -62,6 +62,10 @@
* Intel EtherExpress 16 support from if_ix.c, written by Rodney W. Grimes.
*/
+typedef void Xcopy( void volatile *, void volatile *, int);
+#define VBCOPY(A,B,L) (*(Xcopy *)bcopy)((A),(B),(L))
+typedef void Xzero( void volatile *, int);
+#define VBZERO(A,L) (*(Xzero *)bzero)((A),(L))
/*
* The i82586 is a very versatile chip, found in many implementations.
* Programming this chip is mostly the same, but certain details differ
@@ -219,9 +223,10 @@
/*
* This tells the autoconf code how to set us up.
*/
+static char drivername[] = ie;
struct isa_driver iedriver = {
INTR_TYPE_NET,
- ieprobe, ieattach, ie
+ ieprobe, ieattach, drivername
};
enum ie_hardware {
@@ -776,7 +781,7 @@
ifp-if_softc = ie;
ifp-if_unit = unit;
- ifp-if_name = iedriver.name;
+ ifp-if_name = drivername;
ifp-if_mtu = ETHERMTU;
printf(ie%d: %s R%d address %6D\n, unit,
ie_hardware_names[ie-hard_type],
@@ -1140,7 +1145,7 @@
/*
* Snarf the Ethernet header.
*/
- bcopy((v_caddr_t) ie-cbuffs[i], (caddr_t) ehp, sizeof *ehp);
+ VBCOPY(ie-cbuffs[i], (caddr_t) ehp, sizeof *ehp);
/* ignore cast-qual warning here */
/*
@@ -1228,7 +1233,7 @@
if (thislen m-m_len - thismboff) {
int newlen = m-m_len - thismboff;
- bcopy((v_caddr_t) (ie-cbuffs[head] + offset),
+ VBCOPY((v_caddr_t) (ie-cbuffs[head] + offset),
mtod(m, v_caddr_t) +thismboff, (unsigned) newlen);
/* ignore cast-qual warning */
m = m-m_next;
@@ -1245,7 +1250,7 @@
* pointers, and so on.
*/
if (thislen m-m_len - thismboff) {
- bcopy((v_caddr_t) (ie-cbuffs[head] + offset),
+ VBCOPY((v_caddr_t) (ie-cbuffs[head] + offset),
mtod(m, caddr_t) +thismboff, (unsigned) thislen);
thismboff += thislen; /* we are this far into the
* mbuf */
@@ -1257,7 +1262,7 @@
* buffer's contents into the current mbuf. Do the
* combination of the above actions.
*/
- bcopy((v_caddr_t) (ie-cbuffs[head] + offset),
+ VBCOPY((v_caddr_t) (ie-cbuffs[head] + offset),
mtod(m, caddr_t) + thismboff, (unsigned) thislen);
m = m-m_next;
thismboff = 0; /* new mbuf, start at the beginning */
@@ -1300,7 +1305,7 @@
struct mbuf *m = 0;
struct ether_header eh;
- bcopy((v_caddr_t) (ie-rframes[num]), rfd,
+ VBCOPY((v_caddr_t) (ie-rframes[num]), rfd,
sizeof(struct ie_recv_frame_desc));
/*
@@ -1400,12 +1405,11 @@
len = 0;
for (m0 = m; m len IE_BUF_LEN; m = m-m_next) {
- bcopy(mtod(m, caddr_t), buffer, m-m_len);
+ VBCOPY(mtod(m, caddr_t), buffer, m-m_len);
