panic in 5.3-stable related to heavy usage and libthr
I updated a machine today to 5.3-STABLE and almost instantly it crashed
when a heavily threaded program ran. (The machine was previously running
5.2-release).
This crash is reproducible under heavy load with four threads using
libthr -- I haven't tested any other variances on this scheme, and I
will be testing 5.3-RELEASE tomorrow to see if it exhibits the same
problems.
relevant info from kgdb, with null pointer goodness.
#23 0x in ?? ()
#24 0xc055681f in sleepq_remove_thread (sq=0x0, td=0x0) at
/data/rootsystem/src/sys/kern/subr_sleepqueue.c:581
#25 0xc0556a16 in sleepq_signal (wchan=0xc2b91320, flags=0, pri=-1) at
/data/rootsystem/src/sys/kern/subr_sleepqueue.c:677
#26 0xc053fa53 in wakeup_one (ident=0xc2b91320) at
/data/rootsystem/src/sys/kern/kern_synch.c:266
#27 0xc0543052 in thr_wake (td=0xc2b91000, uap=0xc2b91000) at
/data/rootsystem/src/sys/kern/kern_thr.c:303
#28 0xc0698c9f in syscall (frame=
{tf_fs = 134742063, tf_es = 134742063, tf_ds = -1078001617, tf_edi
= 134558784, tf_esi = 135229440, tf_ebp = -1079198052, tf_isp =
-378659468, tf_ebx = 671863452, tf_edx = 134558792, tf_ecx = 0, tf_eax =
443, tf_trapno = 22, tf_err = 2, tf_eip = 672179195, tf_cs = 31,
tf_eflags = 662, tf_esp = -1079198096, tf_ss = 47}) at
/data/rootsystem/src/sys/i386/i386/trap.c:1001
#29 0xc0686c1f in Xint0x80_syscall () at
/data/rootsystem/src/sys/i386/i386/exception.s:201
Is this useful to anyone? I'll keep this around if you need to poke at
any structures.
- lucas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 'Shared object "libc.so.4" not found' when running FreeBSD 4 command on 5.3
On Thu, Dec 23, 2004 at 12:24:49PM +0900, Hideki Yamamoto wrote: > > Hi, > > When trying to run my application, which was compiled on FreeBSD4.8, > on FreeBSD 5.3, It does not work and appears >'Shared object "libc.so.4" not found.' > > After make an symbolic link as follows, > # ln -s /usr/lib/libc.so /usr/lib/libc.so.4 > it works well. > > Is this link is correct for this problem? No! > My kernel config file includes 'options COMPAT_FREEBSD4' line. > I wonder if this option has some problems. No, that's just the kernel compatibility. To run dynamically-linked 4.x binaries, you need to install the misc/compat4x package. Kris pgpYmJEH6Bn52.pgp Description: PGP signature
New xorg packages uploaded
I've uploaded a new package set for 5.x built against the new x.org 6.8.1 X Windows version. It will make its' way to the ftp servers when they next update. Kris pgpZnajsvEnjt.pgp Description: PGP signature
Re: 'Shared object "libc.so.4" not found' when running FreeBSD 4 command on 5.3
On Thu, Dec 23, 2004 at 12:24:49PM +0900, Hideki Yamamoto wrote: > When trying to run my application, which was compiled on FreeBSD4.8, > on FreeBSD 5.3, It does not work and appears >'Shared object "libc.so.4" not found.' > > After make an symbolic link as follows, > # ln -s /usr/lib/libc.so /usr/lib/libc.so.4 > it works well. > > Is this link is correct for this problem? It may work, but it's not recommended. A recommended solution is that you either re-compile the application, or install ports/misc/compat4x/ so you get libc.so.4. > My kernel config file includes 'options COMPAT_FREEBSD4' line. > I wonder if this option has some problems. This should not be painful :-) If you have many 4-STABLE binaries then you will want this. Cheers, -- Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. pgpUQSTKu4P3x.pgp Description: PGP signature
5.3-STABLE/alpha: re(4) slowdown
After updating my 5.3-STABLE/alpha from Dec 4 to Dec 22 on RELENG_5, network _receiving_ throughput on its re(4) interface has collapsed to a maximum of 0.5-1.0 MB/s. (Figures from scp. Yes, I realize this is not the most suitable test, but the box is not CPU starved and used to receive data at several times that rate.) I use the machine as X11 display and quickly noticed that remote X11 apps had become unusually slow. IPv4 and v6 are equally affected. There haven't been any changes to if_re.c in this period. Any other changes that could explain this? -- Christian "naddy" Weisgerber [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
'Shared object "libc.so.4" not found' when running FreeBSD 4 command on 5.3
Hi, When trying to run my application, which was compiled on FreeBSD4.8, on FreeBSD 5.3, It does not work and appears 'Shared object "libc.so.4" not found.' After make an symbolic link as follows, # ln -s /usr/lib/libc.so /usr/lib/libc.so.4 it works well. Is this link is correct for this problem? My kernel config file includes 'options COMPAT_FREEBSD4' line. I wonder if this option has some problems. Best regards, Hideki Yamamoto - Hideki YAMAMOTO | Broadband Media Solutions Department | E-mail: [EMAIL PROTECTED] Broadband Media Company | Tel: +81-48-420-7012 Oki Electric Industry Co., Ltd. | FAX: +81-48-420-7016 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
slow system freeze
Hello, I'm having a Problem with FreeBSD 5.3 here. The system slowly freezes. It starts with one application that just locks up. Other applications still work, but when I switch to them and do stuff in them, they usually lock up after a few seconds as well. Starting new processes or logging in at a physical console does not work anymore, and after about 30 secs the whole system is frozen. Nothing is printed to the first physical console or the logs. This has happened both under load and while the system was mostly idle (just me irc'ing). Now, I realize that this description is very vague, but maybe you can tell me how to even start debugging this? There's no panic, ie no kernel dump I could analyze. I'm no kernel developer, but if I had to guess it sounds like a scheduler problem, ie some table being overwritten. I've attached my dmesg for reference. Greetings Benjamin Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE-p2 #20: Thu Dec 2 03:52:21 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MERLIN WARNING: MPSAFE network stack disabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3500+ (2210.09-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0xff0 Stepping = 0 Features=0x78bfbff AMD Features=0xe050 real memory = 1073676288 (1023 MB) avail memory = 1036861440 (988 MB) ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf0-0xcf3,0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xf5002000-0xf5002fff irq 22 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xf5003000-0xf5003fff irq 21 at device 2.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0: mem 0xf5004000-0xf50040ff irq 20 at device 2.2 on pci0 ehci0: [GIANT-LOCKED] ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered pci0: at device 5.0 (no driver attached) pci0: at device 6.0 (no driver attached) atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xdc00-0xdc0f,0xb60-0xb63,0x960-0x967,0xbe0-0xbe3,0x9e0-0x9e7 irq 20 at device 9.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pcib1: at device 11.0 on pci0 pci1: on pcib1 nvidia0: mem 0xe800-0xefff,0xf000-0xf0ff irq 16 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] pcib2: at device 14.0 on pci0 pci2: on pcib2 pcm0: port 0xa000-0xa01f irq 18 at device 8.0 on pci2 pcm0: pci2: at device 9.0 (no driver attached) pci2: at device 9.1 (no driver attached) re0: port 0xa800-0xa8ff mem 0xf300-0xf3ff irq 16 at device 13.0 on pci2 miibus0: on re0 rgephy0: on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto re0: Ethernet address: 00:11:09:65:fc:0e re0: [GIANT-LOCKED] fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model MouseMan+, device ID 0 pmtimer0 on isa0 orm0: at iomem 0xd6000-0xd6fff,0xd4000-0xd57ff,0xd-0xd3fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled Timecounter "TSC" frequency 2210091664 Hz quality 800 Timecounters tick every 1
Re: CPUTYPE changes ? (RELENG_5)
Apparently, the CPU type changes have some unintended side effects. For me, they render the system unbootable. I have been investigating what broke my system between a 10th December cvsup and a 20th December one and it boils down to bsd.cpu.mk. I am on a Centrino laptop, which uses a Pentium M (Pentium III with some additional features) CPU. I have CPUTYPE set to "pentium-m". I know this is officially not documented, but bsd.cpu.ml recognizes it and sets the compiler flags accordingly. Unfortunately, something is wrong with the flags. Some feature gets enabled that this CPU does not support and a freshly compiled kernel simply reboots the box on startup. It also affects the boot loader, which shows a register dump for a split second and then reboots the machine as well. I'd love to get to the root of this as currently, it prevents me from keeping my machine up-to-date since anything newer than 15th December leads to an unbootable system :(. - Bartosz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acpi boot error messages after last update (Dec 22nd)
Federico Galvez-Durand Besnard <[EMAIL PROTECTED]> writes: > Hi, just compiled new kernel with lattest acpi. > I am getting boot error messages. > I set hint.acpi.0.disabled="1" in device.hints. > With acpi disabled I get this: > > ( partial dmesg ) > ... > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > unknown: can't assign resources (memory) > unknown: can't assign resources (irq) > unknown: can't assign resources (port) > unknown: can't assign resources (irq) > unknown: can't assign resources (port) > unknown: can't assign resources (port) > unknown: can't assign resources (port) > Timecounter "TSC" frequency 646825914 Hz quality 800 > Timecounters tick every 10.000 msec > ... I don't see any error messages there. What is the actual problem? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp trouble with 5.3-stable
Moin, am Sonntag, 21. November 2004 01:32 schrieb Frank J. Beckmann: > a few days ago a did an upgrade from something pre 5.3-rc7 to the latest > 5.3-stable. Since then I have only trouble with ppp. My computer is > connectet to the internet via pppoe (FreeNet in Germany). My provider > closes the connection once every 24 ours, but ppp now fails to redial. That problem is solved. I had to explicitly disaable eveery possible compression protocil, then it worked. The strange thing ist that it workt before withou disabling that protocols. > The interactive interface of ppp is broken, too: > > kairo:~# pppctl /var/run/tun0.socket > Password: > PPP ON kairo> show > Use ``show ?'' to get a list. > PPP ON kairo> show ? > (o) = Optional context, (c) = Context required > Connection closed > kairo:~# > > Almost every command behaves that way. This problem still exists. I have the impression that pppctl has a problem with shell meta characters. -- Tschüss Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sound blaster ISA 64 Gold and ACPI problem solved on 5-STABLE?
Hello again, It works ok with ACPI enabled! Thanks for fixing that! Today I've tryed to install OSS with and without ACPI without success because of intermitent noise, but this issue has nothing to to with this lists. Thanks again, NUno Teixeira On Mon, Dec 20, 2004 at 01:57:23PM -0800, Nate Lawson wrote: > Nuno Teixeira wrote: > >Hello to all, > > > >I've tryed to use an old SB AWE ISA Gold on FreeBSD 5.2.1 without > >success because it have problems with ACPI enabled. This sound card only > >works with ACPI disabled. > > > >I'd like to know if anyone knows if it works ok on 5-STABLE without > >problem with ACPI. I remember having this problem with OSS and FreeBSD > >native driver. > > I don't know. You can get a CD ISO from snapshots.jp.freebsd.org and > test yourself. We did fix some irq routing problems between 5.2.1 and 5.3. > > -- > Nate -- SDF Public Access UNIX System - http://sdf.lonestar.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CPUTYPE changes ? (RELENG_5)
Hi Mike, On Wed, Dec 22, 2004 at 01:51:51PM -0500, Mike Tancsa wrote: > > I have in the past used > CPUTYPE=i686 > > in /etc/make.conf > > > > But today, I am getting > > > > # make buildworld > "Makefile.inc1", line 117: CPUTYPE global should be set with ?=. > *** Error code 1 > > Stop in /usr/src. > # > > This no longer seems to work. What is the correct syntax for this ? > The error shouldn't have happened, it's intended only for cross-builders (those should be setting this variable with the ?= operator, to allow it to be overridden). I've just committed a fix in src/Makefile.inc1,v 1.471. You can pull up the fix and apply it to RELENG_5. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpOqvp63X2NZ.pgp Description: PGP signature
acpi boot error messages after last update (Dec 22nd)
Hi, just compiled new kernel with lattest acpi. I am getting boot error messages. I set hint.acpi.0.disabled="1" in device.hints. With acpi disabled I get this: ( partial dmesg ) ... vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounter "TSC" frequency 646825914 Hz quality 800 Timecounters tick every 10.000 msec ... Last cvsup on Dec. 22nd. uname -a: FreeBSD here.org 5.3-STABLE FreeBSD 5.3-STABLE #20: Wed Dec 22 20:31:43 GMT-1 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HERE i386 I hope it is only my old notebook Toshiba 2805-s302. Bye. Fico// ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems re-building a FreeBSD 4.x box
Hello, I have a 4.9-STABLE box that I'm willing to upgrade to a newer version (but still on 4.x branch). I tried the usual, cvsup'ed to RELENG_4, went to /usr/src and proceeded with a make buildworld. It failed with these messages: cc -O -pipe -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/config -I. -D__FBSDID=__RCSID -c /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c: In function `forget_protocol_qualifiers': /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:153: `wordlist' undeclared (first use in this function) /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:153: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:153: for each function it appears in.) /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:153: sizeof applied to an incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c: In function `remember_protocol_qualifiers': /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:164: `wordlist' undeclared (first use in this function) /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:164: sizeof applied to an incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c: In function `init_lex': /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:284: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:284: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:288: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:288: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:289: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:289: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:290: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:290: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:291: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:291: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:292: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:292: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:293: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:293: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:294: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:294: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:295: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:295: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:298: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:298: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:302: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:302: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:303: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:303: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:304: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:304: dereferencing pointer to incomplete type /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c:305: warning: initialization makes pointer from integer without a cast /usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c
Re: TIMEOUT - WRITE_DMA retrying (2 retries left)
I two have been seeing this same issue with both 4.9 and 5.3 different messages though and i have yet to find a solution to it here are my messages that im getting from 5.3 ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=6707519 ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=6514167 from 4.9 ad0s1b: UDMA ICRC error writing fsbn 8412383 of 1060432-1060439 (ad0s1 bn 8412383; cn 523 tn 164 sn 56) retrying ad0s1b: UDMA ICRC error writing fsbn 7571295 of 639888-639895 (ad0s1 bn 7571295; cn 471 tn 74 sn 18) retrying and the only time that i really see this error message come up is when theres heavy disk I/O such as durring a portupgrade -arRCc - Original Message - From: "Oleksiy Yakimovych" <[EMAIL PROTECTED]> To: Sent: Wednesday, December 22, 2004 10:03 AM Subject: Re: TIMEOUT - WRITE_DMA retrying (2 retries left) > Hi Steve, > > As far as I know this is not a hardware problem. > Probably there is such DMA problem in 5.3. > Read freebsd-stable mail archive. And I think the problem is not only > with > SATA driver. > So, probably we should wait for a fix :) > > Regards, > Alexei > > "Steve" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > Ok, using a new motherboard, ASUS A7V600-X, was using a A7V133. Same > CPU, > > same disk drives. > > > > On the old motherboard, I never ever had this message. > > > > On the new motherboard, I get it every few hours. Sample logs at the > end. > > > > This is on FreeBSD 5.2.1. I see old messages about this around the > net, in > > most every case, people have their machine lock up. There were > suggestions > > this was a drive issue, not likely as it works on the old motherboard. > > > Also, I saw other people who switched machines and the problem went > away. > > But, I have yet to lock or fail. I saw others who said their files get > > > corrupted, so far, have not seen that happen either. We HAVE seen one > > machine who loses connections to Samba hosted files on this server, > but > > only one machine, so that may be unrelated. > > > > So, I guess my question is this - is there a workaround, software > wise? > > Does anyone have this message but not any problems? Any other clues as > to > > why this happens? Suggestions? Is it likely an upgrade to 5.3 will > cause > > this to go away, any specific fixes that may affect this? Anyone else > have > > the A7V600-X motherboard and does NOT have this issue? > > > > Please remove the trailing "me" on my email address if you wish to > reply > > directly to me on the email address, the domain as is will not work! > > > > Steve > > > > > > ad0: 114473MB [232581/16/63] at ata0-master > UDMA100 > > GEOM: create disk ad1 dp=0xc6b24c60 > > > > atapci1: port 0xa800-0xa80f irq 14 at > device > > 15.1 on pci0 > > ata0: at 0x1f0 irq 14 on atapci1 > > ata0: [MPSAFE] > > > > > > Dec 21 02:58:23 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 > retries > > left) LBA=287 > > Dec 21 07:04:02 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 > retries > > left) LBA=122872179 > > Dec 21 09:37:57 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 > retries > > left) LBA=122841791 > > Dec 21 10:05:17 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 > retries > > left) LBA=3749759 > > Dec 21 11:02:33 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 > retries > > left) LBA=3885087 > > Dec 21 11:03:44 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 > retries > > left) LBA=3623135 > > Dec 21 11:05:04 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 > retries > > left) LBA=3885087 > > > > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CPUTYPE changes ? (RELENG_5)
On Wed, Dec 22, 2004 at 01:51:51PM -0500, Mike Tancsa wrote: > > I have in the past used > CPUTYPE=i686 > > in /etc/make.conf > > > > But today, I am getting > > > > # make buildworld > "Makefile.inc1", line 117: CPUTYPE global should be set with ?=. > *** Error code 1 > > Stop in /usr/src. > # > > This no longer seems to work. What is the correct syntax for this ? Set CPUTYPE with ?= instead of = ;-) Kris pgptswmLROH10.pgp Description: PGP signature
Re: CPUTYPE changes ? (RELENG_5)
from /usr/share/examples/etc/make.conf # Currently the following CPU types are recognized: # Intel x86 architecture: # (AMD CPUs) athlon-mp athlon-xp athlon-4 athlon-tbird athlon # k6-3 # k6-2 k6 k5 # (Intel CPUs)p4 p3 p2 i686 i586/mmx i586 i486 i386 # Alpha/AXP architecture: ev67 ev6 pca56 ev56 ev5 ev45 ev4 # Intel ia64 architecture: itanium # # (?= allows to buildworld for a different CPUTYPE.) # #CPUTYPE?=i686 #NO_CPU_CFLAGS= true# Don't add -march= to CFLAGS automatically #NO_CPU_COPTFLAGS=true # Don't add -march= to COPTFLAGS #automatically # Mike Tancsa <[EMAIL PROTECTED]> schrieb: > > I have in the past used > CPUTYPE=i686 > > in /etc/make.conf > > > > But today, I am getting > > > > # make buildworld > "Makefile.inc1", line 117: CPUTYPE global should be set with ?=. > *** Error code 1 > > Stop in /usr/src. > # > > This no longer seems to work. What is the correct syntax for this ? [...] Dirk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
manpages for devfs.conf and devfs.rules (docs/63808)
Hi all, As a new FreeBSD user I missed manpages for devfs.conf and devfs.rules. This is also listed in GNATS as docs/63808. So I tried my hand at writing them. I've posted them on my website at http://www.xs4all.nl/~rsmith/freebsd/ About two weeks ago I sent a message to the freebsd-doc mailing list, but received no reply or comment sofar. Later I saw that manpages belong to the base system, and not to the documentation project. So if anybody has feedback, and/or pointers where to submit them, I'd be gratefull. Roland -- R.F. Smith /"\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \Respect for open standards pgp2NeH41WR5Z.pgp Description: PGP signature
CPUTYPE changes ? (RELENG_5)
I have in the past used CPUTYPE=i686 in /etc/make.conf But today, I am getting # make buildworld "Makefile.inc1", line 117: CPUTYPE global should be set with ?=. *** Error code 1 Stop in /usr/src. # This no longer seems to work. What is the correct syntax for this ? The rest is fairly generic CPUTYPE=i686 PERL_VER=5.8.5 PERL_VERSION=5.8.5 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo KERNCONF=west1 CFLAGS=-O -pipe COPTFLAGS=-O -pipe NO_MODULES=true# do not build modules with the kernel MODULES_WITH_WORLD=true # do not build modules when building kernel ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: TIMEOUT - WRITE_DMA retrying (2 retries left)
Hi Steve, As far as I know this is not a hardware problem. Probably there is such DMA problem in 5.3. Read freebsd-stable mail archive. And I think the problem is not only with SATA driver. So, probably we should wait for a fix :) Regards, Alexei "Steve" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Ok, using a new motherboard, ASUS A7V600-X, was using a A7V133. Same CPU, > same disk drives. > > On the old motherboard, I never ever had this message. > > On the new motherboard, I get it every few hours. Sample logs at the end. > > This is on FreeBSD 5.2.1. I see old messages about this around the net, in > most every case, people have their machine lock up. There were suggestions > this was a drive issue, not likely as it works on the old motherboard. > Also, I saw other people who switched machines and the problem went away. > But, I have yet to lock or fail. I saw others who said their files get > corrupted, so far, have not seen that happen either. We HAVE seen one > machine who loses connections to Samba hosted files on this server, but > only one machine, so that may be unrelated. > > So, I guess my question is this - is there a workaround, software wise? > Does anyone have this message but not any problems? Any other clues as to > why this happens? Suggestions? Is it likely an upgrade to 5.3 will cause > this to go away, any specific fixes that may affect this? Anyone else have > the A7V600-X motherboard and does NOT have this issue? > > Please remove the trailing "me" on my email address if you wish to reply > directly to me on the email address, the domain as is will not work! > > Steve > > > ad0: 114473MB [232581/16/63] at ata0-master UDMA100 > GEOM: create disk ad1 dp=0xc6b24c60 > > atapci1: port 0xa800-0xa80f irq 14 at device > 15.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci1 > ata0: [MPSAFE] > > > Dec 21 02:58:23 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 retries > left) LBA=287 > Dec 21 07:04:02 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 retries > left) LBA=122872179 > Dec 21 09:37:57 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 retries > left) LBA=122841791 > Dec 21 10:05:17 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 retries > left) LBA=3749759 > Dec 21 11:02:33 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 retries > left) LBA=3885087 > Dec 21 11:03:44 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 retries > left) LBA=3623135 > Dec 21 11:05:04 linux kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 retries > left) LBA=3885087 > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fxp device timeout
Hello all, I have a 2*PentiumPro200 PC with FreeBSD 5.3 acting as a firewall in a department network. The PC has both IDE and SCSI hard drives. (Quite strange system for a firewall, isn't it? However, it was the most suitable box I was able to find). It has 3 NICs xl0,fxp0 and fxp1. >From time to time both fxp's SIMULTANEOUSLY stop working and produce messages fxp*: device timeout. After doing ifconfig fxp* up& down it said Dec 22 19:22:13 firewall kernel: fxp1: SCB timeout: 0x70 0x0 0x50 0x0 Dec 22 19:22:13 firewall kernel: fxp1: SCB timeout: 0x20 0x0 0x50 0x0 Dec 22 19:22:23 firewall last message repeated 53 times Dec 22 19:22:23 firewall kernel: fxp0: SCB timeout: 0x70 0x0 0x50 0x0 Dec 22 19:22:23 firewall kernel: fxp1: SCB timeout: 0x20 0x0 0x50 0x0 The system resumes normal operation only after system reboot. xl0 does not experience any problems. Does anybody know how to avoid this? Many thanks in advance. Here is the output of pciconf -l -v [EMAIL PROTECTED]:0:0: class=0x00 card=0x chip=0x04848086 rev=0x88 hdr=0x00 vendor = 'Intel Corporation' device = '82378ZB/IB,82379AB PCI to ISA Bridge, System I/O' class= old subclass = non-VGA display device [EMAIL PROTECTED]:1:0: class=0x01018a card=0x chip=0x06461095 rev=0x01 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'PCI-0646 EIDE Adapter (Single FIFO)' class= mass storage subclass = ATA [EMAIL PROTECTED]:2:0: class=0x01 card=0x chip=0x80789004 rev=0x00 hdr=0x00 vendor = 'Adaptec Inc' device = 'AIC-7880P Ultra/Ultra Wide SCSI Chipset' class= mass storage subclass = SCSI [EMAIL PROTECTED]:11:0:class=0x03 card=0x chip=0x0519102b rev=0x01 hdr=0x00 vendor = 'Matrox Electronic Systems Ltd.' device = 'MGA-2064W Storm (Millennium board)' class= display subclass = VGA [EMAIL PROTECTED]:12:0: class=0x02 card=0x100010b7 chip=0x920010b7 rev=0x6c hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905C-TX Fast EtherLink for PC Management NIC' class= network subclass = ethernet [EMAIL PROTECTED]:13:0: class=0x02 card=0x1200103c chip=0x12298086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class= network subclass = ethernet [EMAIL PROTECTED]:14:0: class=0x02 card=0x1200103c chip=0x12298086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class= network subclass = ethernet [EMAIL PROTECTED]:20:0:class=0x05 card=0x chip=0x84c58086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82453KX/GX 450KX/GX Memory Controller (Orion)' class= memory subclass = RAM [EMAIL PROTECTED]:25:0: class=0x06 card=0x chip=0x84c48086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82454KX/GX 450KX/GX Orion System Controller' class= bridge subclass = HOST-PCI * Here is the output of dmesg -a: ** FreeBSD 5.3-RELEASE #0: Sat Dec 18 11:45:40 MSK 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/FIREWALL Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium Pro (199.74-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 100663296 (96 MB) avail memory = 88842240 (84 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 ioapic0: Changing APIC ID to 16 ioapic0: Assuming intbase of 0 MPTable: Ignoring global interrupt entry for pin 1 MPTable: Ignoring global interrupt entry for pin 2 MPTable: Ignoring global interrupt entry for pin 3 MPTable: Ignoring global interrupt entry for pin 4 MPTable: Ignoring global interrupt entry for pin 5 MPTable: Ignoring global interrupt entry for pin 6 MPTable: Ignoring global interrupt entry for pin 7 MPTable: Ignoring global interrupt entry for pin 8 MPTable: Ignoring global interrupt entry for pin 9 MPTable: Ignoring global interrupt entry for pin 10 MPTable: Ignoring global interrupt entry for pin 11 MPTable: Ignoring global interrupt entry for pin 12 MPTable: Ignoring global interrupt entry for pin 13 MPTable: Ignoring global interrupt entry for pin 14 MPTable: Ignoring global interrupt entry for pin 15 ioapic0 irqs 0-15 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 isab0: at device 0.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 14 at device 1.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ahc0: port 0xf800-0xf8ff mem 0xffbfc000-0xffbfcff
Re: Fixing Posix semaphores
--- Peter Pentchev <[EMAIL PROTECTED]> wrote: > On Wed, Dec 22, 2004 at 12:01:51AM +, Robert > Watson wrote: > > > > On Mon, 13 Dec 2004, Joe Kelsey wrote: > > > > > I have a desire to fix posix semaphores in at > least 5.3. The current > > > implementation doesn't actually follow the > "spirit" of the standard, > > > even though it technically qualifies in a > somewhat degraded sense. I > > > refer to the fact that the current > implementation treats posix > > > semaphores as completely contained inside the > kernel and essentially > > > divorced from the filesystem. The true "spirit" > of the standard places > > > the semaphores directly in the file system, > similar to named pipes. > > > However the current implementation treats the > supplied "name" as a > > > 14-character identifier, required to begin with > a slash and contain no > > > other slashes. Pretty weak. > > > > > > Well, in order to fix this, we need to add file > system code and come up > > > with a new type. I currently have some time to > spend on something like > > > this and am willing to put in whatever effort it > takes. Does anyone > > > want to add their own ideas or requirements? > > > > >From my perspective, the biggest win here is that > it would permit > > different name spaces to trivially exist using > multiple mountpoints of a > > "semfs". This would make it easy to allow > applications in different jails > > to use identical names without colliding. > > > > FWIW, my only experience with POSIX semaphores on > a system other than > > FreeBSD is on Darwin, where a similar model is > used to that on FreeBSD: a > > flat kernel-maintained name space is present. > > I seem to remember either W. Richard Stevens's APUE, > or Marc Rochkind's > AUP stating that: > > 1. the standards say that semaphore names ought to > have filesystem >semantics, but... > 2. the standards leave it to the implementation to > define whether >slashes should be allowed at all except in the > first position, so... But the Posix 1003.1 does require that afully qualified pathname be supported by the interface. > 3. portable programs should only depend on a flat > namespace, >especially as... > 4. there are widely-used OS's (ISTR Solaris, but > ICBW) that only provide >a flat namespace. > > Thus, it would seem that even if somebody would do > the work to really > tie the semaphore naming fully to the filesystem, > still programs that > want to be Really Really Portable would not dare use > this feature, > wonderful as it would be for those that do :( > Well -the issue was about providing support to the interface so that it can handle a fully qualified pathname. If a programmer wants to use a flat namespace to ensure that his program is portable onto other OS'es that don't adhere to the std -that is a different issue [which does not put it in conflict with the std]. BTW -I see no reason why pathnames should be tied to the filesystem, instead of being used simply as identifiers across processes. regards -kamal > G'luck, > Peter > > -- > Peter Pentchev[EMAIL PROTECTED][EMAIL PROTECTED] > [EMAIL PROTECTED] > PGP key: > http://people.FreeBSD.org/~roam/roam.key.asc > Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 > B68D 1619 4553 > What would this sentence be like if pi were 3? > > ATTACHMENT part 2 application/pgp-signature __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
IBM ServeRAID 7k & 5.3
[just for a record] Hi all, It seems ips(4) doesn't support ServeRAID 7k, however I just installed 5.3-RELEASE/i386 on IBM x236 which has ServeRAID 7k installed. Everything looks fine here (I'm running RAID-5 over 4 HDDs). A little problem is that once a HDD fails, FreeBSD doesn't know that unless I reboot it and saw the ips state is DEGRADED. pciconf & dmesg are listed as below: [EMAIL PROTECTED]:14:0: class=0x010400 card=0x028e1014 chip=0x02509005 rev=0x07 hdr=0x00 vendor = 'Adaptec Inc' class= mass storage subclass = RAID ips0: mem 0xcfffd000-0xcfffdfff irq 38 at device 14.0 on pci3 ips0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xcfffd000 ips0: [GIANT-LOCKED] ips0: logical drives: 1 ips0: Logical Drive 0: RAID5 sectors: 430116864, state OK ipsd0: on ips0 ipsd0: Logical Drive (210018MB) Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Will there be a 5.3.1?
On Wed, Dec 22, 2004 at 02:25:14PM +, Pete French wrote: > > The type of a decimal integer constant without any suffix is the first > > of 'int', 'long', 'long long' in which the constant can be represented. > > It is ? Well, you learn something new every day I guess! I stand > corrected in that case. Appologies. > > > (For C89 it was the first of 'int', 'long', 'unsigned long') > > ...and before that ? Did this behaviour change at the end of the 80's - I > don't actually recall seeing it on any compilers after 88 or so I have > to admit. Before that it was just the first of 'int' and 'long'. (According to Harbison/Steele: C:A Reference Manual) > > > No doubt, but if it does the compilers are buggy. > > Apparently so. It seems I've spent the last 18 years or so believing an > untyped integer constant was always of type 'int' when it wasn't true. Well, > maybe I will be less anal about adding 'L' to the ends of my constants from > now on. > > -pcf. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP vulnerability and portupgrade
Mark Andrews said: >> Thanks a lot for your reply. If I understand things correctly, I need to >> maintain two cvsup files - one that tracks security issues in the base >> FreeBSD 5.3 system (tag=RELENG_5_3, src-all) and one for the ports >> collection (tag=. , ports-all). Then every time I receive a FreeBSD >> security advisory I run cvsup on the former, and every time portaudit tells >> me about a new security issue in the ports collection, I run cvsup on the >> latter, then use portupgrade to upgrade vulnerable ports. >> >> Is this correct? > > Essentually. When you install portaudit it will be run as > part of the daily periodic jobs provided the FreeBSD version > is new enough (which 5.3 is). Portaudit gets added to the daily periodic scripts on 4.10 also. And contrary to name, portaudit will also watch for vulnerabilities in the base system. For example, the cvs issue from awhile back showed up in my portaudit results. Thus, it's not strictly necessary to always keep your base system source up to date as long as your system is stable and you're watching the portaudit results. -- Charles Ulrich Ideal Solution, LLC - http://www.idealso.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Will there be a 5.3.1?
On Wed, 22 Dec 2004 14:25:14 + Pete French <[EMAIL PROTECTED]> wrote: > > The type of a decimal integer constant without any suffix is the first > > of 'int', 'long', 'long long' in which the constant can be represented. > > It is ? Well, you learn something new every day I guess! I stand > corrected in that case. Appologies. > > > (For C89 it was the first of 'int', 'long', 'unsigned long') > > ...and before that ? Did this behaviour change at the end of the 80's - I > don't actually recall seeing it on any compilers after 88 or so I have > to admit. Getting -1 is a bug even in K&R C, unless long is 16 bits :) -- C:>WIN | Directable Mirror Arrays The computer obeys and wins.| A better way to focus the sun You lose and Bill collects. |licences available see |http://www.sohara.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Samba, NTFS & FreeBSD 5-STABLE.
Hello, when I export NTFS volume mounted on FreeBSD-STABLE (FreeBSD sysadm.stc 5.3-STABLE FreeBSD 5.3-STABLE #0: Fri Dec 17 18:49:45 MSK 2004) via Samba, then I get strange effect: When accessing share (from Windows or from localhost via smbclient) all directories appear as files with 0 size, when I try access it, then Windows asks how to open this file. After first access, file reappears as directory. Maybe this is Samba bug, but does anyone have same problem? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Will there be a 5.3.1?
> The type of a decimal integer constant without any suffix is the first > of 'int', 'long', 'long long' in which the constant can be represented. It is ? Well, you learn something new every day I guess! I stand corrected in that case. Appologies. > (For C89 it was the first of 'int', 'long', 'unsigned long') ...and before that ? Did this behaviour change at the end of the 80's - I don't actually recall seeing it on any compilers after 88 or so I have to admit. > No doubt, but if it does the compilers are buggy. Apparently so. It seems I've spent the last 18 years or so believing an untyped integer constant was always of type 'int' when it wasn't true. Well, maybe I will be less anal about adding 'L' to the ends of my constants from now on. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Will there be a 5.3.1?
On Wed, Dec 22, 2004 at 12:26:03PM +, Pete French wrote: > > Buggy compilers are indefensible, yes, but why try to apologise for it? > > I dont see it as a bug. Without an 'L' the right hand side of that > expression is a 16 bit int. For which 65536 is out of range. If I > wrote 'int y = 65535; long x = y;' then I would get the same result for > the same reason. Wrong. With 16-bit int the constant 65536 has type long. The type of a decimal integer constant without any suffix is the first of 'int', 'long', 'long long' in which the constant can be represented. (For C89 it was the first of 'int', 'long', 'unsigned long') (See 6.4.4.1 in the C99 standard.) Your example of 'int y = 65535; long x = y;' on the other hand causes implementation-defined behaviour for 16-bit ints. (As do all other instances of overflow for signed integer types.) > > The correct line is 'long x = 65535L;' which specifies that the constant > is a long. In fact aren't situations like this the precise reason for > having the 'L' as part of the language ? > > > 'long x = 65535;' will not set x to -1, even with 16-bit ints. > > It will and does on certain compilers unfortunately. No doubt, but if it does the compilers are buggy. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to enable ACLs on /?
Hi, maybe it ist a faq, but I didn't find it in the list archive. How do I enable ACLs on / in FreeBSD 5.3? I tried to boot into single user mode and did tunefs -a enable /dev/ad4s2a and ACLs are enabled. But they are not enabled anymore as soon as I mount /. But as long as / is not mounted, the ACLs show to be enabled. -- Tschüss Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Will there be a 5.3.1?
> Buggy compilers are indefensible, yes, but why try to apologise for it? I dont see it as a bug. Without an 'L' the right hand side of that expression is a 16 bit int. For which 65536 is out of range. If I wrote 'int y = 65535; long x = y;' then I would get the same result for the same reason. The correct line is 'long x = 65535L;' which specifies that the constant is a long. In fact aren't situations like this the precise reason for having the 'L' as part of the language ? > 'long x = 65535;' will not set x to -1, even with 16-bit ints. It will and does on certain compilers unfortunately. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Booting problem on HP Compaq DC7100
Hello. I'm running a HP Compaq DC7100 with two S-ATA harddrives. It's a bit difficult for me to say what goes wrong, because I'm not told. I've installed FreeBSD, and when I turn on the computer it passes on to the bootloader part. This is where, when I select F1 for FreeBSD (F5 is Drive1 and used to run Windows, but after the FreeBSD MBR alteration it will not boot either), the computer *simply* reboots. If I use the standard MBR and not the bootloader, it will just continue to try to load FreeBSD and then reboot in an infinite loop. I've tried seeking answers on [EMAIL PROTECTED], on IRC and on Google. But nobody seems to be familiar with newer hardware. I've tried messing around in my BIOS setup, playing with most of the available options but to no good. I've tried setting the FreeBSD harddrive partition to bootable, as well as resetted the MBR with fdisk. My superiors, what could i do to *fix* this? Thanks, Johann -- j. pgpItXGtAVucz.pgp Description: PGP signature
acpiconf -s3 and time
hello, i use 5.3-STABLE, and have noticed, that if i run acpiconf -s3 (hard sleep ?) on my laptop, all is fine, but the current time "freezes", so if i power my laptop later on, i have the same time as before sleep it is very ..er..unpleasant to set up time after each sleep again i am not sure, but think that some version before this worked, so question is how to make it work again :) -- # If it happens once, it's a bug. # If it happens twice, it's a feature. # If it happens more then twice, it's a design philosophy. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
