Re: sparc64 tinderbox failure
Peter Wemm [EMAIL PROTECTED] writes: Mike Barcroft wrote: stage 4: building everything.. -- === share/man/man9 make: don't know how to make bus_Activate_resource.9. Stop *** Error code 2 This looks like a single bit memory error to me. Turn off bit 5 and a lowercase a turns into an uppercase A. nice try, but check rev 1.179 of src/share/man/man9/Makefile. 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: Unclean sync in current
Thus spake Kevin Oberman [EMAIL PROTECTED]:
I've been seeing this for a couple of weeks since I updated my laptop to
CURRENT. I do a normal shutdown (-p or -r) and reboot. The shutdown
looked normal, with no problems reported with the sync, but, when the
system is rebooted, the partitions are all shown as possibly
unclean. From my dmesg:
Mounting root from ufs:/dev/ad0s3a
WARNING: / was not properly dismounted
WARNING: / was not properly dismounted
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
WARNING: /var was not properly dismounted
All disks are mounted with soft-updates enabled.
I don't see any other reports of this. Is this unique to my system?
Unlike the SCSI driver, the ATA driver does not send a flush cache
command to your disks before powering off the system. The kernel
waits for five seconds in either case, but for some disks that may
not be sufficient.
The following patch should fix that, although it may have rotted a
bit in the last two months given Soeren's sweeping ATA changes. I
also edited an unrelated change out of the diff, which might
confuse patch(1). If you run into problems getting it to apply,
let me know and I'll fix it when I'm back from vacation.
Index: sys/dev/ata/ata-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.163
diff -u -r1.163 ata-all.c
--- sys/dev/ata/ata-all.c 2003/01/19 20:18:07 1.163
+++ sys/dev/ata/ata-all.c 2003/01/27 09:17:02
@@ -77,6 +77,7 @@
static void ata_intr(void *);
static int ata_getparam(struct ata_device *, u_int8_t);
static int ata_service(struct ata_channel *);
+static void ata_shutdown(void *arg, int howto);
static void bswap(int8_t *, int);
static void btrim(int8_t *, int);
static void bpack(int8_t *, int8_t *, int);
@@ -1160,7 +1161,32 @@
return error;
}
+/*
+ * This procedure is called during shutdown,
+ * after all dirty buffers have been flushed.
+ */
static void
+ata_shutdown(void *arg, int howto)
+{
+struct ata_channel *ch;
+int ctlr;
+
+#ifdef DEV_ATADISK
+/* Flush the caches of each open ATA disk device. */
+for (ctlr = 0; ctlr devclass_get_maxunit(ata_devclass); ctlr++) {
+ if (!(ch = devclass_get_softc(ata_devclass, ctlr)))
+ continue;
+ ch-lock_func(ch, ATA_LF_LOCK);
+ if (ch-devices ATA_ATA_MASTER ch-device[MASTER].driver)
+ ad_sync(ch-device[MASTER]);
+ if (ch-devices ATA_ATA_SLAVE ch-device[SLAVE].driver)
+ ad_sync(ch-device[SLAVE]);
+ ch-lock_func(ch, ATA_LF_UNLOCK);
+}
+#endif /* DEV_ATADISK */
+}
+
+static void
ata_drawer_start(struct ata_device *atadev)
{
ATA_INB(atadev-channel-r_io, ATA_DRIVE);
@@ -1516,5 +1542,10 @@
printf(ata: config_intrhook_establish failed\n);
free(ata_delayed_attach, M_TEMP);
}
+
+/* Register a handler to flush write caches on shutdown */
+if ((EVENTHANDLER_REGISTER(shutdown_post_sync, ata_shutdown,
+ NULL, SHUTDOWN_PRI_DEFAULT)) == NULL)
+ printf(ata: shutdown event registration failed!\n);
}
SYSINIT(atadev, SI_SUB_DRIVERS, SI_ORDER_SECOND, ata_init, NULL)
Index: sys/dev/ata/ata-disk.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v
retrieving revision 1.139
diff -u -r1.139 ata-disk.c
--- sys/dev/ata/ata-disk.c 2002/12/17 16:26:22 1.139
+++ sys/dev/ata/ata-disk.c 2003/01/27 09:17:04
@@ -255,10 +255,8 @@
disk_invalidate(adp-disk);
disk_destroy(adp-dev);
devstat_remove_entry(adp-stats);
-if (flush) {
- if (ata_command(atadev, ATA_C_FLUSHCACHE, 0, 0, 0, ATA_WAIT_READY))
- ata_prtdev(atadev, flushing cache on detach failed\n);
-}
+if (flush)
+ ad_sync(atadev);
if (adp-flags AD_F_RAID_SUBDISK)
ata_raiddisk_detach(adp);
ata_free_name(atadev);
@@ -289,8 +287,7 @@
adp-device-channel-lock_func(adp-device-channel, ATA_LF_LOCK);
ATA_SLEEPLOCK_CH(adp-device-channel, ATA_CONTROL);
-if (ata_command(adp-device, ATA_C_FLUSHCACHE, 0, 0, 0, ATA_WAIT_READY))
- ata_prtdev(adp-device, flushing cache on close failed\n);
+ad_sync(adp-device);
ATA_UNLOCK_CH(adp-device-channel);
adp-device-channel-lock_func(adp-device-channel, ATA_LF_UNLOCK);
return 0;
@@ -765,6 +762,20 @@
return ATA_OP_CONTINUES;
}
return ATA_OP_FINISHED;
+}
+
+/*
+ * Flush the write cache of the given device.
+ */
+int
+ad_sync(struct ata_device *atadev)
+{
+int error;
+
+/* XXX The ATA standard says this command can take up to 30 seconds. */
+if ((error = ata_command(atadev,ATA_C_FLUSHCACHE,0,0,0,ATA_WAIT_READY)))
+ ata_prtdev(atadev, flushing cache failed\n);
+return error;
}
static void
Index: sys/dev/ata/ata-disk.h
===
Re: several background fsck panics
Thus spake Alexander Langer [EMAIL PROTECTED]: I had several panics related to background fsck now. Once I disabled background fsck, all went ok. It began when I pressed the reset buttons on several boots while the system was still doing fscks. [...] Mar 24 21:48:59 fump kernel: panic: ufs_dirbad: bad dir You would have gotten this one without bgfsck as well the next time you tried to look the offending directory. Background fsck only expedited the panic by reading all the directories on the system in order to perform its checks. Basically, the panic is the kernel's way of telling you that something is unexpectedly wrong with the filesystem (due in this case to ATA write caching), and that it is going to give up rather than risk causing further damage. UFS, as well as most other filesystems, are not designed to tolerate failures on the part of the hardware to honor its guarantees, so it's hard to do better without inventing a new filesystem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Re: several background fsck panics
Thus spake Terry Lambert [EMAIL PROTECTED]: o Put a counter in the first superblock; it would be incremented when the BG fsck is started, and reset to zero when it completes. If the counter reaches 3 (or some command line specified number), then the BG flagging is ignored, and a full FG fsck is then performed instead. I like this idea because it will always work, and it's not actually a hack, it's a correct solution. I'm glad you like it because AFAIK, it is already implemented. ;-) o Implement soft read-only. The place that most of the complaints are coming from is desktop users, with relatively quiescent machines. Though swap is used, it does not occur in an FS partition. As a result, the FS could be marked read-only for long period of time. This marking would be in memory. The clean bit would be set on the superblock. When a write occurs, the clean bit would be reset to dirty, and committed to disk prior to the write operation being permitted to proceed (a stall barrier). I like this idea because, for the most part, it eliminates fsck, both BG and FG, on systems that crash while it's in effect. The net result is a system that is statistically much more tolerant of failures, but which still requires another safety net, such as the previous solution. I was thinking of doing something like this myself as part of an ``idle timeout'' for disks. (Marking the filesystem clean after a period of quiescence would actually interfere with ATA disks' built-in mechanism for spinning down after a timeout, which is important for laptops, so the OS would have to track the true amount of idle time.) Annoyingly, I can never get the disk containing /var to remain quiescent for long while cron is running (even without any crontabs), and I hope this can be solved without disabling cron or adding a nontrivial hack to bio. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ATA broken on alpha?
beast.freebsd.org is panicing at bootup with this: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #81: Sun Mar 30 07:48:29 PST 2003 [EMAIL PROTECTED]:/usr/src/sys/alpha/compile/BEAST Preloaded elf kernel /boot/kernel/kernel at 0xfc714000. ST6600 AlphaPC 264DP 833 MHz, 833MHz 8192 byte page size, 2 processors. CPU: EV6 (21264) major=8 minor=0 extensions=0x1307BWX,FIX,CIX,MVI,PRECISE OSF PAL rev: 0x200370002013e real memory = 2144706560 (2045 MB) avail memory = 2081095680 (1984 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Allocating major#253 to net Allocating major#252 to g_ctl Allocating major#251 to pci tsunami0: 21271 Core Logic chipset pcib0: 21271 PCI host bus adapter on tsunami0 pci0: PCI bus on pcib0 isab0: PCI-ISA bridge at device 5.0 on pci0 isa0: ISA bus on isab0 atapci0: Cypress 82C693 ATA controller port 0x1300-0x130f,0x3f4-0x3f7,0x1f0-0x1f7 irq 238 at device 5.1 on pci0 fatal kernel trap: trap entry = 0x2 (memory management fault) cpuid = 0 faulting va= 0x0 type = access violation cause = load instructon pc = 0xfc37b0fc ra = 0xfc37b0d0 sp = 0xfc71ba50 usp= 0x0 curthread = 0xfc63d3f8 pid = 0, comm = swapper Stopped at ata_pcisub_probe+0x11c: ldl t0,0(t0) 0x0 t0=0x0 db trace ata_pcisub_probe() at ata_pcisub_probe+0x11c device_probe_child() at device_probe_child+0x114 device_probe_and_attach() at device_probe_and_attach+0x58 bus_generic_attach() at bus_generic_attach+0x28 ata_pci_attach() at ata_pci_attach+0x600 device_probe_and_attach() at device_probe_and_attach+0xc4 bus_generic_attach() at bus_generic_attach+0x28 pci_attach() at pci_attach+0xe0 device_probe_and_attach() at device_probe_and_attach+0xc4 bus_generic_attach() at bus_generic_attach+0x28 device_probe_and_attach() at device_probe_and_attach+0xc4 bus_generic_attach() at bus_generic_attach+0x28 tsunami_attach() at tsunami_attach+0x98 device_probe_and_attach() at device_probe_and_attach+0xc4 root_bus_configure() at root_bus_configure+0x38 configure() at configure+0x40 mi_startup() at mi_startup+0x144 locorestart() at locorestart+0x64 --- root of call graph --- Do you need more details or is that enough of a clue? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA broken on alpha?
It seems Peter Wemm wrote: Do you need more details or is that enough of a clue? I can see what the problem is, I'll have to look to find the reason... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Do we want to let cpp(1) hide warnings in system headers?
On Sun, Mar 30, 2003 at 09:09:18AM +0300, Ruslan Ermilov wrote: On Sat, Mar 29, 2003 at 03:19:05PM -0800, David O'Brien wrote: On Thu, Mar 13, 2003 at 08:08:54PM +0200, Ruslan Ermilov wrote: Sigh. It's been a while since I've fixed the feature of gcc(1) that makes it hide warnings in system headers (but visible with -nostdinc -I/usr/include). What is the difference in output from make buildworld? Lot of (non-fatal) warnings. I was hoping you'd acutally show some of the increased warning output. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Newbie build problem
Hi, I've been R-ing the FWP but haven't had any luck so far: Specifically, when I try to make buildworld I get: === usr.bin/yacc /shared/FreeBSD-current/shared/FreeBSD-current/usr/src/usr.bin/yacc created for /shared/FreeBSD-current/usr/src/usr.bin/yacc sh /shared/FreeBSD-current/usr/src/tools/install.sh -s -o root -g wheel -m 555 yacc /shared/FreeBSD-current/usr/bin sh /shared/FreeBSD-current/usr/src/tools/install.sh -o root -g wheel -m 555 yy fix.sh /shared/FreeBSD-current/usr/bin/yyfix install: /shared/FreeBSD-current/usr/bin/yyfix: Not a directory *** Error code 71 Stop in /shared/FreeBSD-current/usr/src/usr.bin/yacc. *** Error code 1 Stop in /shared/FreeBSD-current/usr/src. *** Error code 1 Stop in /shared/FreeBSD-current/usr/src. *** Error code 1 Stop in /shared/FreeBSD-current/usr/src. This is with the tree cvsup'd into /shared/FreeBSD-current. Am I supposed to create the bin directory by hand? I thought the makefile would build directories it needs. My make.conf looks like this: # -- use.perl generated deltas -- # # Created: Thu Mar 6 04:17:57 2003 # Setting to use base perl from ports: PERL_VER=5.6.1 PERL_VERSION=5.6.1 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo MAKEOBJDIRPREFIX=/shared/FreeBSD-current NOGAMES=true Any pointers would be helpful. I've spent a lot of time on this webpage: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html But it seems to be out of date as some files on it don't exist in 5.0. Thanks for any help! Gordon = -- Gordon Zaft [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with clock (fwd)
-- Forwarded message -- Date: Fri, 28 Mar 2003 23:18:35 +0100 (CET) From: Friedemann Becker [EMAIL PROTECTED] To: Andris [EMAIL PROTECTED] Subject: Re: Problems with clock Try this one. I had the same problem, and de fix described put the clock back to normal operation. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/32226 On Fri, 28 Mar 2003, Andris wrote: Hi everyone! I have strange problems with my PC clock. Clock seems to be ~2 times faster. What's up? Andris Here is dmesg output: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-RELEASE-p6 #0: Fri Mar 28 11:45:46 EET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MEZHS Preloaded elf kernel /boot/kernel/kernel at 0xc0407000. Preloaded elf module /boot/kernel/acpi.ko at 0xc04070a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 333516074 Hz CPU: AMD-K6(tm) 3D processor (333.52-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 134152192 (127 MB) avail memory = 125931520 (120 MB) Initializing GEOMetry subsystem K6-family MTRR support enabled (2 registers) VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c4eeb (c0004eeb) VESA: S3 Incorporated. 86C775/86C785 npx0: math processor on motherboard npx0: INT 16 interface acpi0: ALi_ on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 Using $PIR table, 6 entries at 0xc00f7c40 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 32-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 acpi_cpu0: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Ali M1541 host to AGP bridge mem 0xd000-0xd1ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci0: bridge, PCI-unknown at device 3.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 pci0: display, VGA at device 8.0 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xdc00-0xdcff mem 0xebfeff00-0xebfe irq 10 at device 9.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:30:4f:16:8f:79 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xdf80-0xdf9f irq 9 at device 10.0 on pci0 ed0: address 00:48:45:00:07:9e, type NE2000 (16 bit) atapci0: AcerLabs Aladdin ATA33 controller port 0xffa0-0xffaf at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 acpi_button0: Sleep Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: cmd 3 failed at out byte 1 of 3 ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: Printer on ppbus0 lpt0: Interrupt-driven port sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: cmd 3 failed at out byte 1 of 3 orm0: Option ROM at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 fdc0: cannot reserve I/O port range (6 ports) sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, logging unlimited DUMMYNET initialized (011031) IP Filter: v3.4.29 initialized. Default = pass all, Logging = enabled acpi_cpu: CPU throttling enabled, 8 steps from 100% to 12.5% ad0: 3098MB ST33210A [6296/16/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s1a ___ [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: ypserv and sshd not getting along in -current
At 02:55 PM 29/03/03, Terry Lambert sent this up the stick: Glenn Johnson wrote: I can not login to a box with FreeBSD 5 -current via ssh because I get the following error from ypserv: Mar 28 12:48:15 node1 ypserv[317]: access to master.passwd.byuid denied -- client 192.168.1.1:49344 not privileged man ypbind (-s is the magic incantation). I have the same issue, I tried Terry's suggestion but I don't think its working like it should: On the client: aylee # ps fax|grep yp 252 ?? Is 0:0.62 /usr/sbin/ypbind -s aylee # rpcinfo -p localhost|grep yp 17 2 udp 1022ypbind 17 2 tcp 1023ypbind Tailing the server's log: Mar 31 10:10:39 erwin ypserv[92]: access to master.passwd.byuid denied -- client 192.168.100.30:49255 not privileged Why would the request be coming from a high port when I have specifically told it to bind to a low port? Cheers, Rob -- On Earth there is no reckoning. This is random quote 883 of 1254. Distance from the centre of the brewing universe [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ypserv and sshd not getting along in -current
On Mon, Mar 31, 2003 at 10:46:07AM +1000, Rob B wrote: At 02:55 PM 29/03/03, Terry Lambert sent this up the stick: Glenn Johnson wrote: I can not login to a box with FreeBSD 5 -current via ssh because I get the following error from ypserv: Mar 28 12:48:15 node1 ypserv[317]: access to master.passwd.byuid denied -- client 192.168.1.1:49344 not privileged man ypbind (-s is the magic incantation). I have the same issue, I tried Terry's suggestion but I don't think its working like it should: On the client: aylee # ps fax|grep yp 252 ?? Is 0:0.62 /usr/sbin/ypbind -s aylee # rpcinfo -p localhost|grep yp 17 2 udp 1022ypbind 17 2 tcp 1023ypbind Tailing the server's log: Mar 31 10:10:39 erwin ypserv[92]: access to master.passwd.byuid denied -- client 192.168.100.30:49255 not privileged Why would the request be coming from a high port when I have specifically told it to bind to a low port? The answer (work around) is to turn off PrivelegeSeparation in your sshd_config file. -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Do we want to let cpp(1) hide warnings in system headers?
On Sun, Mar 30, 2003 at 02:07:20PM -0800, David O'Brien wrote: On Sun, Mar 30, 2003 at 09:09:18AM +0300, Ruslan Ermilov wrote: On Sat, Mar 29, 2003 at 03:19:05PM -0800, David O'Brien wrote: On Thu, Mar 13, 2003 at 08:08:54PM +0200, Ruslan Ermilov wrote: Sigh. It's been a while since I've fixed the feature of gcc(1) that makes it hide warnings in system headers (but visible with -nostdinc -I/usr/include). What is the difference in output from make buildworld? Lot of (non-fatal) warnings. I was hoping you'd acutally show some of the increased warning output. Without this, cpp(1) doesn't warn about redefinitions in system headers, that's how I hit this bug. Cheers, -- Ruslan Ermilov Sysadmin and 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 pgp0.pgp Description: PGP signature
Re: unrecognized Prism III card
: I picked up a couple of no-name Prism III cards, and found that : FreeBSD-current doesn't recognize them. Is there anything I can do to : make these work? (Up to and including shipping a card to a : committer?) Ship me a dozen :-) At least tell me their name so I can do the support right... However, short of that, let's try the following patch: The same kind of patch should work for an Asus WL-100 in sys/dev/pccard/pccarddevs: product ASUS WL_100 0x0002 WL-100 vendor ASUS 0x02aa ASUS And in sys/dev/wi/if_wi_pccard.c: PCMCIA_CARD(ASUS, WL_100, 0), Makes it work for me. (It's a Prism2.5 card) Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
isnan() with gcc 3.2.2 on FreeBSD 5.0-C
the following code snippet works fine with gcc 2.95.4 on RELENG_4
but failed on my -current
code
#include iostream
#include cmath
using namespace std;
int main(void)
{
cout isnan(1.0) endl;
return 0;
}
/code
err
test.cpp: In function `int main()':
test.cpp:8: `isnan' undeclared (first use this function)
test.cpp:8: (Each undeclared identifier is reported only once for each function
it appears in.)
/err
what's wrong with my system ? or what can I do for it ?
--
int i;main(){for(;i[]i;++i){--i;}];read('-'-'-',i+++hell\
o, world!\n,'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
-- IOCCC 1984
pgp0.pgp
Description: PGP signature
