Re: diskio / filesystem related deadlock on SMP 6.0-STABLE machine.
Kris Kennaway said the following on 1/26/2006 3:46 PM: On Thu, Jan 26, 2006 at 06:44:22PM -0500, Kris Kennaway wrote: On Thu, Jan 26, 2006 at 06:37:16PM -0500, Mike Jakubik wrote: Kris Kennaway wrote: On Thu, Jan 26, 2006 at 05:07:56PM +0200, Niki Denev wrote: On Thursday 26 January 2006 10:40, Niki Denev wrote: [...] After i disabled option QUOTA in both my default kernel config and the one i compiled with the debugging options i was unable to reproduce the deadlock again. (i hope it stays that way :) ) This, together with the report in my previous post probably point that the problem is in the QUOTA support. Actually, I think this is known. Kris Well thats good to know, i was planning on upgrading a production box from 5 to 6, its SMP and uses QUOTA. How did 6 get released when QUOTA was known to cause deadlocks? FYI, you can probably work around this by setting debug.mpsafevfs=0. Of course, you'll lose the filesystem performance benefits. Kris I'd like to confirm that setting debug.mpsafevfs=0 (along with debug.mpsafevm=0 and debug.mpsafenet=0) doesn't help either. I ran into the same problem about a month ago on 2 production boxes running 6-STABLE (SMP with QUOTA enabled) and the only way I found to stop them crashing was switching back to 5.4. I hope this will get fixed in 6.1. Regards, Atanas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on i386/pc98
TB --- 2006-01-27 07:02:52 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-27 07:02:52 - starting RELENG_6 tinderbox run for i386/pc98 TB --- 2006-01-27 07:02:52 - cleaning the object tree TB --- 2006-01-27 07:03:36 - checking out the source tree TB --- 2006-01-27 07:03:36 - cd /tinderbox/RELENG_6/i386/pc98 TB --- 2006-01-27 07:03:36 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2006-01-27 07:31:26 - building world (CFLAGS=-O -pipe) TB --- 2006-01-27 07:31:26 - cd /src TB --- 2006-01-27 07:31:26 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] gzip -cn /src/lib/bind/lwres/../../../contrib/bind9/lib/lwres/man/lwres_packet.3 lwres_packet.3.gz gzip -cn /src/lib/bind/lwres/../../../contrib/bind9/lib/lwres/man/lwres_resutil.3 lwres_resutil.3.gz === libexec (all) === libexec/atrun (all) cc -O -pipe -DATJOB_DIR=\/var/at/jobs/\ -DLFILE=\/var/at/jobs/.lockfile\ -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\/var/at/spool\ -DVERSION=\2.9\ -DDAEMON_UID=1 -DDAEMON_GID=1 -DDEFAULT_BATCH_QUEUE=\'E\' -DDEFAULT_AT_QUEUE=\'c\' -DPERM_PATH=\/var/at/\ -I/src/libexec/atrun/../../usr.bin/at -I/src/libexec/atrun -c /src/libexec/atrun/atrun.c cc -O -pipe -DATJOB_DIR=\/var/at/jobs/\ -DLFILE=\/var/at/jobs/.lockfile\ -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\/var/at/spool\ -DVERSION=\2.9\ -DDAEMON_UID=1 -DDAEMON_GID=1 -DDEFAULT_BATCH_QUEUE=\'E\' -DDEFAULT_AT_QUEUE=\'c\' -DPERM_PATH=\/var/at/\ -I/src/libexec/atrun/../../usr.bin/at -I/src/libexec/atrun -c /src/libexec/atrun/gloadavg.c cc -O -pipe -DATJOB_DIR=\/var/at/jobs/\ -DLFILE=\/var/at/jobs/.lockfile\ -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\/var/at/spool\ -DVERSION=\2.9\ -DDAEMON_UID=1 -DDAEMON_GID=1 -DDEFAULT_BATCH_QUEUE=\'E\' -DDEFAULT_AT_QUEUE=\'c\' -DPERM_PATH=\/var/at/\ -I/src/libexec/atrun/../../usr.bin/at -I/src/libexec/atrun -o atrun atrun.o gloadavg.o /obj/pc98/src/tmp/usr/lib/libc.so: undefined reference to `calloc' *** Error code 1 Stop in /src/libexec/atrun. *** Error code 1 Stop in /src/libexec. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-27 08:19:10 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-27 08:19:10 - ERROR: failed to build world TB --- 2006-01-27 08:19:10 - tinderbox aborted TB --- 1.17 user 5.20 system 4577.35 real ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskio / filesystem related deadlock on SMP 6.0-STABLE machine.
Atanas wrote: Kris Kennaway said the following on 1/26/2006 3:46 PM: On Thu, Jan 26, 2006 at 06:44:22PM -0500, Kris Kennaway wrote: On Thu, Jan 26, 2006 at 06:37:16PM -0500, Mike Jakubik wrote: Kris Kennaway wrote: On Thu, Jan 26, 2006 at 05:07:56PM +0200, Niki Denev wrote: On Thursday 26 January 2006 10:40, Niki Denev wrote: [...] After i disabled option QUOTA in both my default kernel config and the one i compiled with the debugging options i was unable to reproduce the deadlock again. (i hope it stays that way :) ) This, together with the report in my previous post probably point that the problem is in the QUOTA support. Actually, I think this is known. Kris Well thats good to know, i was planning on upgrading a production box from 5 to 6, its SMP and uses QUOTA. How did 6 get released when QUOTA was known to cause deadlocks? FYI, you can probably work around this by setting debug.mpsafevfs=0. Of course, you'll lose the filesystem performance benefits. Kris I'd like to confirm that setting debug.mpsafevfs=0 (along with debug.mpsafevm=0 and debug.mpsafenet=0) doesn't help either. I ran into the same problem about a month ago on 2 production boxes running 6-STABLE (SMP with QUOTA enabled) and the only way I found to stop them crashing was switching back to 5.4. I hope this will get fixed in 6.1. So do I! I'm quite surprised to hear of such a huge bug this late. I had plans in place to upgrade a few clients to 6-STABLE but this information changes a few of them. Hopefully someone knowledgeable enough will look in to this, unfortunately i can't test any code changes... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.0-STABLE Totally Freezes on TightVNC Connection
Russell Doucette wrote: Mike Jakubik wrote: It's either a hardware problem, or some serious issue with ipf. As a side note, i would highly recommend you ditch ipf and switch to pf instead, its a much better firewall. Yeah, I fixed it. I switched network cards and the BSD box works fine now. It was either the network driver or the network card itself. Thanks for the help. Great, which network card was it? I still recommend you switch to PF :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on sparc64/sparc64
TB --- 2006-01-27 08:19:11 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-27 08:19:11 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2006-01-27 08:19:11 - cleaning the object tree TB --- 2006-01-27 08:19:48 - checking out the source tree TB --- 2006-01-27 08:19:48 - cd /tinderbox/RELENG_6/sparc64/sparc64 TB --- 2006-01-27 08:19:48 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2006-01-27 08:43:41 - building world (CFLAGS=-O -pipe) TB --- 2006-01-27 08:43:41 - cd /src TB --- 2006-01-27 08:43:41 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] gzip -cn /src/lib/bind/lwres/../../../contrib/bind9/lib/lwres/man/lwres_packet.3 lwres_packet.3.gz gzip -cn /src/lib/bind/lwres/../../../contrib/bind9/lib/lwres/man/lwres_resutil.3 lwres_resutil.3.gz === libexec (all) === libexec/atrun (all) cc -O -pipe -DATJOB_DIR=\/var/at/jobs/\ -DLFILE=\/var/at/jobs/.lockfile\ -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\/var/at/spool\ -DVERSION=\2.9\ -DDAEMON_UID=1 -DDAEMON_GID=1 -DDEFAULT_BATCH_QUEUE=\'E\' -DDEFAULT_AT_QUEUE=\'c\' -DPERM_PATH=\/var/at/\ -I/src/libexec/atrun/../../usr.bin/at -I/src/libexec/atrun -c /src/libexec/atrun/atrun.c cc -O -pipe -DATJOB_DIR=\/var/at/jobs/\ -DLFILE=\/var/at/jobs/.lockfile\ -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\/var/at/spool\ -DVERSION=\2.9\ -DDAEMON_UID=1 -DDAEMON_GID=1 -DDEFAULT_BATCH_QUEUE=\'E\' -DDEFAULT_AT_QUEUE=\'c\' -DPERM_PATH=\/var/at/\ -I/src/libexec/atrun/../../usr.bin/at -I/src/libexec/atrun -c /src/libexec/atrun/gloadavg.c cc -O -pipe -DATJOB_DIR=\/var/at/jobs/\ -DLFILE=\/var/at/jobs/.lockfile\ -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\/var/at/spool\ -DVERSION=\2.9\ -DDAEMON_UID=1 -DDAEMON_GID=1 -DDEFAULT_BATCH_QUEUE=\'E\' -DDEFAULT_AT_QUEUE=\'c\' -DPERM_PATH=\/var/at/\ -I/src/libexec/atrun/../../usr.bin/at -I/src/libexec/atrun -o atrun atrun.o gloadavg.o /obj/sparc64/src/tmp/usr/lib/libc.so: undefined reference to `calloc' *** Error code 1 Stop in /src/libexec/atrun. *** Error code 1 Stop in /src/libexec. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-27 09:16:45 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-27 09:16:45 - ERROR: failed to build world TB --- 2006-01-27 09:16:45 - tinderbox aborted TB --- 0.81 user 3.96 system 3454.45 real ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: smb_maperror: Unmapped error 1:158
Steve Hodgson wrote: Mike Jakubik wrote: Jan 26 17:01:47 desktop kernel: smb_maperror: Unmapped error 1:158 Jan 26 17:02:18 desktop last message repeated 52 times Jan 26 17:04:19 desktop last message repeated 646 times Jan 26 17:14:20 desktop last message repeated 6342 times I get this message frequently, almost every time I access my media library over samba. I have always put it down to a character encoding issue, but I have never investigated it properly since it's been there since I started using freebsd. I've certainly never had a crash or hang associated with these messages. I've tried setting the encoding to ASCII on both client and server, but it made no difference. I think this error should be investigated. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fxp0: device timeout and sk0: watchdog timeout problems
On Wednesday 18 January 2006 00:36, Pyun YongHyeon wrote: atm I have no clue. How about updated sk(4)? http://people.freebsd.org/~yongari/sk/if_sk.c http://people.freebsd.org/~yongari/sk/if_skreg.h Hi again I am running your both versions (UP and SMP) now for almost 10 days without any problem. I think the problem is gone! thank's a lot João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hi all.. Novice user having woes getting Atheros card up in FreeBSD 6.0
On Thu, 2006-Jan-26 20:10:56 -0800, resonant evil wrote: Hi there.. So I can't use this wireless card at all right now? Damn why did I buy this thing then.. People from the mailing list showed me this one so I ordered it :-( That exact card, or that model number? One major problem with PC hardware is that vendors regularly update the electronics without changing the model designations. This doesn't affect Windoze users because they provide updated drivers to match. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
How do I turn off hyperthreading on 6.0 ?
I though that machdep.hyperthreading_allowed had to be set to 1 to turn on hyperthreading ? I have a dual processor HP blade, and when I boot it up with an SMP kernel I get 4 CPU's. Setting that flag does not have any effect! Any thoughts ? I dont think I have two CPU's each with dual core and without hyperthreading somehow! (though the thought did cross my mind...) [EMAIL PROTECTED] sysctl machdep.hyperthreading_allowed machdep.hyperthreading_allowed: 0 CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3600.14-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf43 Stepping = 3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x659dSSE3,RSVD2,MON,DS_CPL,EST,TM2,CNTX-ID,CX16,b14 AMD Features=0x2000LM Hyperthreading: 2 logical CPUs real memory = 3758043136 (3583 MB) avail memory = 3678736384 (3508 MB) ACPI APIC Table: HP 0083 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskio / filesystem related deadlock on SMP 6.0-STABLE machine.
Quoting Kris Kennaway [EMAIL PROTECTED]: On Thu, Jan 26, 2006 at 06:44:22PM -0500, Kris Kennaway wrote: On Thu, Jan 26, 2006 at 06:37:16PM -0500, Mike Jakubik wrote: Kris Kennaway wrote: On Thu, Jan 26, 2006 at 05:07:56PM +0200, Niki Denev wrote: On Thursday 26 January 2006 10:40, Niki Denev wrote: [...] After i disabled option QUOTA in both my default kernel config and the one i compiled with the debugging options i was unable to reproduce the deadlock again. (i hope it stays that way :) ) This, together with the report in my previous post probably point that the problem is in the QUOTA support. Actually, I think this is known. Kris Well thats good to know, i was planning on upgrading a production box from 5 to 6, its SMP and uses QUOTA. How did 6 get released when QUOTA was known to cause deadlocks? FYI, you can probably work around this by setting debug.mpsafevfs=0. Of course, you'll lose the filesystem performance benefits. I encounter the same problem (kern/91631) and debug.mpsafevfs=0 don't solve the issue! I have to disable quota in etc/rc.conf.local and /etc/fstab to go around the problem (options QUOTA is still in my kernel config). The system is running for 6 days now and I cross my fingers... I intend to send a follow-up to the PR after 15 days of uptime. Henri Kris This message was sent using IMP, the Internet Messaging Program. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
if_bge driver problem.
Hi, I upgraded my pc after 2006-01-25 FreeBSD-SA-06:06.kmem issue. After that it also upgrade the bge drivers and now it is not working. In fact my Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 is not working. The other bge's working properly. Most probly last update may cause that. I have been using 6-STABLE. I also tried to look at the switch part and find out that there are CRC Errors. The errors comes just after enabling the interface on the bsd box. After that there isnt any activity. Also when I sniff the interface with tcpdump, I saw lots of packets. Most probly, the driver did not let the further comminication after bad CRCs. Thanks for the help. Note: Do I have to add a PR to the bug report. Husnu Demir. The details are follows: root@/usr/src# dmesg Copyright (c) 1992-2005 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 6.0-STABLE #0: Fri Jan 27 10:49:49 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NON-GENERIC ACPI APIC Table: IntelR AWRDACPI Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3066.79-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNTX-ID,b14 Hyperthreading: 2 logical CPUs real memory = 2147418112 (2047 MB) avail memory = 2096418816 (1999 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 4 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: IntelR AWRDACPI on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pcib1: PCI-PCI bridge mem 0xec00-0xefff at device 1.0 on pci0 pci1: PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 2.0 on pci0 pci2: ACPI PCI bus on pcib2 pci2: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 29.0 on pci2 pci3: ACPI PCI bus on pcib3 bge0: Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xf102-0xf102 irq 48 at device 1.0 on pci3 miibus0: MII bus on bge0 brgphy0: BCM5703 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:11:09:9b:6a:7d bge1: Broadcom BCM5701 Gigabit Ethernet, ASIC rev. 0x105 mem 0xf100-0xf100 irq 52 at device 2.0 on pci3 miibus1: MII bus on bge1 brgphy1: BCM5701 10/100/1000baseTX PHY on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:04:76:f7:99:6e bge2: Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xf101-0xf101 irq 56 at device 3.0 on pci3 bge2: Ethernet address: 00:10:18:00:4d:53 pci2: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib4: ACPI PCI-PCI bridge at device 31.0 on pci2 pci4: ACPI PCI bus on pcib4 em0: Intel(R) PRO/1000 Network Connection Version - 3.2.18 port 0x9000-0x903f mem 0xf304-0xf305,0xf300-0xf303 irq 28 at device 2.0 on pci4 em0: Ethernet address: 00:04:23:c2:dc:29 mpt0: LSILogic 1030 Ultra4 Adapter port 0x9400-0x94ff mem 0xf306-0xf306,0xf307-0xf307 irq 32 at device 3.0 on pci4 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.12.0 mpt0: Unhandled Event Notify Frame. Event 0xa. mpt0: Capabilities: ( RAID-1 SAFTE ) mpt0: 0 Active Volumes (1 Max) mpt0: 0 Hidden Drive Members (6 Max) mpt1: LSILogic 1030 Ultra4 Adapter port 0x9800-0x98ff mem 0xf308-0xf308,0xf309-0xf309 irq 33 at device 3.1 on pci4 mpt1: [GIANT-LOCKED] mpt1: MPI Version=1.2.12.0 mpt1: Unhandled Event Notify Frame. Event 0xa. mpt1: Capabilities: ( RAID-1 SAFTE ) mpt1: 0 Active Volumes (1 Max) mpt1: 0 Hidden Drive Members (6 Max) pci0: unknown at device 2.1 (no driver attached) uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xb800-0xb81f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801DB (ICH4) USB controller USB-B
Re: dhclient wedged
Kelly, On Sun, 22 Jan 2006, Kelly D. Grills wrote: =On Sun, Jan 22, 2006 at 02:52:44AM -0500, Forrest Aldrich wrote: = = I reported this problem a few OS versions back... pre-6. I'm on = FreeBSD-6-STABLE, and I've found the dhclient once again wedged in a = mode that was eating a lot of CPU. = = The solution is to kill it, and restart. = = I'm on Comcast's network, so I don't really know if their DHCP server is = doing something that FreeBSD's stock dhclient doesn't like; however, I = wonder if someone else has noticed this problem, etc. = =Yes, I've also had the same problem (6.0-RELEASE), on Comcast also. =I installed isc-dhcp3-client-3.0.3_1 from ports and haven't had a =problem since. (crossing fingers ;=) not sure if it's the same problem for you, but Comcast in my area supplies a bad entry for DNS Suffix/Search order ((hsd1.ca.comcast.net)(hsd2.ca.comcast.net)) And my little netgear router doesn't like that entry and _seems_ to only supply hsd1.ca.comcast.net)) via dhcp. My Mac and Winbloze boxes do fine, but FBSD rejects the dhoffer unless isc's dhclient is used. I haven't tried plugging directly into the Comcast router, so I don't know if FBSD will accept the original offer with parens... Thanks, Will -- Will Froning Unix Sys. Admin. [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: if_bge driver problem.
On Fri, Jan 27, 2006 at 02:24:38PM +0200, husnu demir wrote: h Hi, h h I upgraded my pc after 2006-01-25 FreeBSD-SA-06:06.kmem issue. After that it also upgrade the bge drivers and now it is not working. In fact my Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 is not working. The other bge's working properly. Most probly last update may cause that. I have been using 6-STABLE. h h I also tried to look at the switch part and find out that there are CRC Errors. The errors comes just after enabling the interface on the bsd box. After that there isnt any activity. Also when I sniff the interface with tcpdump, I saw lots of packets. Most probly, the driver did not let the further comminication after bad CRCs. What happens if you disable hardware checksum offloading on your NIC? ifconfig bge0 -rxcsum -txcsum -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: if_bge driver problem.
On Fri, Jan 27, 2006 at 02:24:38PM +0200, husnu demir wrote: h I upgraded my pc after 2006-01-25 FreeBSD-SA-06:06.kmem issue. After that it also upgrade the bge drivers and now it is not working. In fact my Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 is not working. The other bge's working properly. Most probly last update may cause that. I have been using 6-STABLE. h h I also tried to look at the switch part and find out that there are CRC Errors. The errors comes just after enabling the interface on the bsd box. After that there isnt any activity. Also when I sniff the interface with tcpdump, I saw lots of packets. Most probly, the driver did not let the further comminication after bad CRCs. Please provide also output from 'pciconf -lv | grep -A 3 ^bge', and from 'ifconfig'. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: if_bge driver problem. - Upgrade to RELEASE :)
Hi Again, I upgraded to the 6_RELEASE; $ uname -a FreeBSD nrouter.cc.metu.edu.tr 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Fri Jan 27 18:03:39 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NON-GENERIC i386 and now it is working. But the CRC errors still exists. I only see the CRC errors on enabling the interface. But the stable still does not work. Husnu Demir. On Fri, Jan 27, 2006 at 06:35:12PM +0300, Gleb Smirnoff wrote: On Fri, Jan 27, 2006 at 02:24:38PM +0200, husnu demir wrote: h I upgraded my pc after 2006-01-25 FreeBSD-SA-06:06.kmem issue. After that it also upgrade the bge drivers and now it is not working. In fact my Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 is not working. The other bge's working properly. Most probly last update may cause that. I have been using 6-STABLE. h h I also tried to look at the switch part and find out that there are CRC Errors. The errors comes just after enabling the interface on the bsd box. After that there isnt any activity. Also when I sniff the interface with tcpdump, I saw lots of packets. Most probly, the driver did not let the further comminication after bad CRCs. Please provide also output from 'pciconf -lv | grep -A 3 ^bge', and from 'ifconfig'. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ 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: if_bge driver problem. - Upgrade to RELEASE :)
On Fri, Jan 27, 2006 at 06:11:51PM +0200, husnu demir wrote: h I upgraded to the 6_RELEASE; h h $ uname -a h FreeBSD nrouter.cc.metu.edu.tr 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Fri Jan 27 18:03:39 EET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NON-GENERIC i386 h h and now it is working. But the CRC errors still exists. I only see the CRC errors on enabling the interface. But the stable still does not work. One more time: please provide also output from 'pciconf -lv | grep -A 3 ^bge', and from 'ifconfig'. Also it is important to know whether doing 'ifconfig bge0 -rxcsum -txcsum' fixes operation on 6.0-STABLE. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: if_bge driver problem.
Nothing changed. and the other infos; Thanks for the quick response. [EMAIL PROTECTED] ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet6 fe80::211:9ff:fe9b:6a7d%bge0 prefixlen 64 scopeid 0x1 inet x.x.3.138 netmask 0xff80 broadcast x.x.3.255 ether 00:11:09:9b:6a:7d media: Ethernet autoselect (100baseTX full-duplex) status: active bge1: flags=8902BROADCAST,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING ether 00:04:76:f7:99:6e media: Ethernet autoselect (none) status: no carrier bge2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=18VLAN_MTU,VLAN_HWTAGGING inet6 fe80::210:18ff:fe00:4d53%bge2 prefixlen 64 scopeid 0x3 inet x.x.2.2 netmask 0xff00 broadcast x.x.2.255 ether 00:10:18:00:4d:53 media: Ethernet autoselect (1000baseSX full-duplex) status: active em0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU ether 00:04:23:c2:dc:29 media: Ethernet autoselect status: no carrier pflog0: flags=0 mtu 33208 pfsync0: flags=0 mtu 2020 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 inet 127.0.0.1 netmask 0xff00 fatm0: flags=841UP,RUNNING,SIMPLEX mtu 9180 inet x.x.16.130 netmask 0xfffc inet x.x.17.2 netmask 0xfffc media: ATM Multi-mode/155MBit status: active [EMAIL PROTECTED] pciconf -lv | grep -A 3 ^bge [EMAIL PROTECTED]:1:0: class=0x02 card=0x026f1014 chip=0x16a714e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703X NetXtreme Gigabit Ethernet' class= network -- [EMAIL PROTECTED]:2:0: class=0x02 card=0x100610b7 chip=0x164514e4 rev=0x15 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5701 NetXtreme Gigabit Ethernet' class= network -- [EMAIL PROTECTED]:3:0: class=0x02 card=0x000a14e4 chip=0x16a714e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703X NetXtreme Gigabit Ethernet' class= network On Fri, Jan 27, 2006 at 06:34:39PM +0300, Gleb Smirnoff wrote: On Fri, Jan 27, 2006 at 02:24:38PM +0200, husnu demir wrote: h Hi, h h I upgraded my pc after 2006-01-25 FreeBSD-SA-06:06.kmem issue. After that it also upgrade the bge drivers and now it is not working. In fact my Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 is not working. The other bge's working properly. Most probly last update may cause that. I have been using 6-STABLE. h h I also tried to look at the switch part and find out that there are CRC Errors. The errors comes just after enabling the interface on the bsd box. After that there isnt any activity. Also when I sniff the interface with tcpdump, I saw lots of packets. Most probly, the driver did not let the further comminication after bad CRCs. What happens if you disable hardware checksum offloading on your NIC? ifconfig bge0 -rxcsum -txcsum -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ 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: if_bge driver problem.
By the way the problem exists on bge2 (with Multimode F/O connector.) Husnu Demir. On Fri, Jan 27, 2006 at 06:35:12PM +0300, Gleb Smirnoff wrote: On Fri, Jan 27, 2006 at 02:24:38PM +0200, husnu demir wrote: h I upgraded my pc after 2006-01-25 FreeBSD-SA-06:06.kmem issue. After that it also upgrade the bge drivers and now it is not working. In fact my Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 is not working. The other bge's working properly. Most probly last update may cause that. I have been using 6-STABLE. h h I also tried to look at the switch part and find out that there are CRC Errors. The errors comes just after enabling the interface on the bsd box. After that there isnt any activity. Also when I sniff the interface with tcpdump, I saw lots of packets. Most probly, the driver did not let the further comminication after bad CRCs. Please provide also output from 'pciconf -lv | grep -A 3 ^bge', and from 'ifconfig'. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient wedged
On Fri, Jan 27, 2006 at 06:30:36AM -0800, Will Froning wrote: Kelly, On Sun, 22 Jan 2006, Kelly D. Grills wrote: =On Sun, Jan 22, 2006 at 02:52:44AM -0500, Forrest Aldrich wrote: = = I reported this problem a few OS versions back... pre-6. I'm on = FreeBSD-6-STABLE, and I've found the dhclient once again wedged in a = mode that was eating a lot of CPU. = = The solution is to kill it, and restart. = = I'm on Comcast's network, so I don't really know if their DHCP server is = doing something that FreeBSD's stock dhclient doesn't like; however, I = wonder if someone else has noticed this problem, etc. = =Yes, I've also had the same problem (6.0-RELEASE), on Comcast also. =I installed isc-dhcp3-client-3.0.3_1 from ports and haven't had a =problem since. (crossing fingers ;=) not sure if it's the same problem for you, but Comcast in my area supplies a bad entry for DNS Suffix/Search order ((hsd1.ca.comcast.net)(hsd2.ca.comcast.net)) I must say that's a really creative one. I wonder if it even works for Windows. And my little netgear router doesn't like that entry and _seems_ to only supply hsd1.ca.comcast.net)) via dhcp. My Mac and Winbloze boxes do fine, but FBSD rejects the dhoffer unless isc's dhclient is used. I haven't tried plugging directly into the Comcast router, so I don't know if FBSD will accept the original offer with parens... If you upgrade to 6.0-STABLE the offer won't be rejected, it will just delete the invalid entry. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpRBidrMG5pi.pgp Description: PGP signature
Re: if_bge driver problem. - Upgrade to RELEASE :)
Also it is important to know whether doing 'ifconfig bge0 -rxcsum -txcsum' fixes operation on 6.0-STABLE. No, It does not fixed. I will go back to STABLE if you need further detail. Husnu Demir. (Note: I may leave the office. will try to contact you las soon as possible.) For RELEASE version; [EMAIL PROTECTED] pciconf -lv | grep -A 3 ^bge [EMAIL PROTECTED]:1:0: class=0x02 card=0x026f1014 chip=0x16a714e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703X NetXtreme Gigabit Ethernet' class= network -- [EMAIL PROTECTED]:2:0: class=0x02 card=0x100610b7 chip=0x164514e4 rev=0x15 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5701 NetXtreme Gigabit Ethernet' class= network -- [EMAIL PROTECTED]:3:0: class=0x02 card=0x000a14e4 chip=0x16a714e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703X NetXtreme Gigabit Ethernet' class= network [EMAIL PROTECTED] ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1aTXCSUM,VLAN_MTU,VLAN_HWTAGGING inet6 fe80::211:9ff:fe9b:6a7d%bge0 prefixlen 64 scopeid 0x1 inet x.x.3.138 netmask 0xff80 broadcast x.x.3.255 ether 00:11:09:9b:6a:7d media: Ethernet autoselect (100baseTX full-duplex) status: active bge1: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=1aTXCSUM,VLAN_MTU,VLAN_HWTAGGING ether 00:04:76:f7:99:6e media: Ethernet autoselect (none) status: no carrier bge2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=18VLAN_MTU,VLAN_HWTAGGING inet6 fe80::210:18ff:fe00:4d53%bge2 prefixlen 64 scopeid 0x3 inet x.x.2.2 netmask 0xff00 broadcast x.x.2.255 ether 00:10:18:00:4d:53 media: Ethernet autoselect (1000baseSX full-duplex) status: active em0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU ether 00:04:23:c2:dc:29 media: Ethernet autoselect status: no carrier lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet 127.0.0.1 netmask 0xff00 pfsync0: flags=0 mtu 2020 pflog0: flags=0 mtu 33208 For STABLE version ; --- [EMAIL PROTECTED] ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet6 fe80::211:9ff:fe9b:6a7d%bge0 prefixlen 64 scopeid 0x1 inet x.x.3.138 netmask 0xff80 broadcast x.x.3.255 ether 00:11:09:9b:6a:7d media: Ethernet autoselect (100baseTX full-duplex) status: active bge1: flags=8902BROADCAST,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING ether 00:04:76:f7:99:6e media: Ethernet autoselect (none) status: no carrier bge2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=18VLAN_MTU,VLAN_HWTAGGING inet6 fe80::210:18ff:fe00:4d53%bge2 prefixlen 64 scopeid 0x3 inet x.x.2.2 netmask 0xff00 broadcast x.x.2.255 ether 00:10:18:00:4d:53 media: Ethernet autoselect (1000baseSX full-duplex) status: active em0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU ether 00:04:23:c2:dc:29 media: Ethernet autoselect status: no carrier pflog0: flags=0 mtu 33208 pfsync0: flags=0 mtu 2020 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 inet 127.0.0.1 netmask 0xff00 [EMAIL PROTECTED] pciconf -lv | grep -A 3 ^bge [EMAIL PROTECTED]:1:0: class=0x02 card=0x026f1014 chip=0x16a714e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703X NetXtreme Gigabit Ethernet' class= network -- [EMAIL PROTECTED]:2:0: class=0x02 card=0x100610b7 chip=0x164514e4 rev=0x15 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5701 NetXtreme Gigabit Ethernet' class= network -- [EMAIL PROTECTED]:3:0: class=0x02 card=0x000a14e4 chip=0x16a714e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703X NetXtreme Gigabit Ethernet' class= network On Fri, Jan 27, 2006 at 06:34:39PM +0300, Gleb Smirnoff wrote: On Fri, Jan 27, 2006 at 02:24:38PM +0200, husnu demir wrote: h Hi, h h I upgraded my pc after 2006-01-25 FreeBSD-SA-06:06.kmem issue. After that it also upgrade the bge drivers and now it is not working. In fact my Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 is not working. The other bge's working properly. Most probly last update may cause that. I have been using 6-STABLE. h h I also tried to look at the switch part and find out that there are CRC Errors.
Re: if_bge driver problem.
On Fri, Jan 27, 2006 at 05:58:18PM +0200, husnu demir wrote: h By the way the problem exists on bge2 (with Multimode F/O connector.) Oh, this is an important information. Can you please upgrade to STABLE and then test several versions of if_bge.c? The breakage is somewhere between rev. 1.101 and 1.113. There is high probability it is one of Oleg's changes. Details here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c All revisions up to the latest should be buildable on 6.0-STABLE. The only place where build can fail is VLAN_INPUT_TAG() macro. You probably need to replace it with VLAN_INPUT_TAG_NEW() if it fails to build. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: if_bge driver problem.
On Fri, Jan 27, 2006 at 07:30:55PM +0300, Gleb Smirnoff wrote: On Fri, Jan 27, 2006 at 05:58:18PM +0200, husnu demir wrote: h By the way the problem exists on bge2 (with Multimode F/O connector.) Oh, this is an important information. Can you please upgrade to STABLE and then test several versions of if_bge.c? The breakage is somewhere between rev. 1.101 and 1.113. There is high probability it is one of Oleg's changes. Details here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c All revisions up to the latest should be buildable on 6.0-STABLE. The only place where build can fail is VLAN_INPUT_TAG() macro. You probably need to replace it with VLAN_INPUT_TAG_NEW() if it fails to build. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE Hi, I tried http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/dev/bge/if_bge.c?rev=1.91.2.7content-type=text/plain; version and replaced VLAN_INPUT_TAG with VLAN_INPUT_TAG_NEW (only one occurance). And the following errors come up. Husnu Demir. Not: I am leaving the office. Most probly, I will be here tomorrow morning :( /usr/src/sys/modules/bge/../../dev/bge/if_bge.c: In function `bge_eeprom_getbyte': /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:574: error: structure has no member named `bge_unit' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c: In function `bge_miibus_readreg': /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:649: error: structure has no member named `bge_unit' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c: In function `bge_miibus_writereg': /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:700: error: structure has no member named `bge_unit' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c: In function `bge_alloc_jumbo_mem': /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:761: error: structure has no member named `bge_jumbo_tag' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:765: error: structure has no member named `bge_unit' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:771: error: structure has no member named `bge_jumbo_tag' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:772: error: structure has no member named `bge_jumbo_buf' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:773: error: structure has no member named `bge_jumbo_map' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:778: error: structure has no member named `bge_jfree_listhead' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:779: error: structure has no member named `bge_jinuse_listhead' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:785: error: structure has no member named `bge_jumbo_buf' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:787: error: structure has no member named `bge_jslots' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:789: error: invalid application of `sizeof' to incomplete type `bge_jpool_entry' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:793: error: structure has no member named `bge_jumbo_buf' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:795: error: structure has no member named `bge_unit' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:798: error: dereferencing pointer to incomplete type /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:799: error: dereferencing pointer to incomplete type /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:799: error: structure has no member named `bge_jfree_listhead' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:799: error: structure has no member named `bge_jfree_listhead' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c: In function `bge_free_jumbo_mem': /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:814: error: structure has no member named `bge_jfree_listhead' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:815: error: structure has no member named `bge_jfree_listhead' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:815: error: structure has no member named `bge_jfree_listhead' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:822: error: structure has no member named `bge_jumbo_tag' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:823: error: structure has no member named `bge_jumbo_buf' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:824: error: structure has no member named `bge_jumbo_map' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:827: error: structure has no member named `bge_jumbo_tag' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:828: error: structure has no member named `bge_jumbo_map' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:830: error: structure has no member named `bge_jumbo_tag' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:831: error: structure has no member named `bge_jumbo_tag' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c: In function `bge_jalloc': /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:845: error: structure has no member named `bge_jfree_listhead' /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:848: error: structure has no member named `bge_unit'
Re: if_bge driver problem.
On Fri, Jan 27, 2006 at 07:01:53PM +0200, husnu demir wrote: h I tried http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/dev/bge/if_bge.c?rev=1.91.2.7content-type=text/plain; version and replaced VLAN_INPUT_TAG with VLAN_INPUT_TAG_NEW (only one occurance). And the following errors come up. Ohh, you also need to keep if_bgereg.h in sync with if_bge.c. Sorry, I didn't mention this. h Not: I am leaving the office. Most probly, I will be here tomorrow morning :( Me too. I will be online tomorrow for short time. I think Oleg will join debugging your problem. Here is attached files of all (if I haven't lost anything) important changes. You can fetch actual files from cvsweb. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE pjd 2005-09-28 19:20:49 UTC FreeBSD src repository Modified files: sys/dev/bge if_bge.c Log: Implement suspend/resume methods to be more ACPI friendly. I'm able to suspend/resume my laptop without this change, but then I need to wait for the watchdog to reset the card. With this change, it is ready immediately. Glanced at by: glebius Revision ChangesPath 1.96 +36 -0 src/sys/dev/bge/if_bge.c glebius 2005-10-22 14:31:02 UTC FreeBSD src repository Modified files: sys/dev/bge if_bge.c if_bgereg.h Log: Introduce polling(4) capability for bge(4). Submitted by: Oleg Bulyzhin oleg rinet.ru Revision ChangesPath 1.98 +110 -2src/sys/dev/bge/if_bge.c 1.37 +3 -0 src/sys/dev/bge/if_bgereg.h glebius 2005-11-15 14:43:23 UTC FreeBSD src repository Modified files: sys/dev/bge if_bge.c if_bgereg.h Log: Recognize Broadcom BCM5752 chip, that can be found in HP DC7600. PR: kern/88940 Submitted by: Alexander Hausner Revision ChangesPath 1.100 +5 -2 src/sys/dev/bge/if_bge.c 1.38 +2 -0 src/sys/dev/bge/if_bgereg.h glebius 2005-11-30 12:37:07 UTC FreeBSD src repository Modified files: sys/dev/bge if_bge.c Log: If bus_dmamap_load() failed, we free the mbuf. We also need to clear the pointer, to avoid double free on next bge_stop(). Revision ChangesPath 1.101 +6 -2 src/sys/dev/bge/if_bge.c oleg2005-12-08 13:31:52 UTC FreeBSD src repository Modified files: sys/dev/bge if_bge.c sys/dev/mii brgphy.c Log: 1) fix tiny bug in bge_start_locked() 2) rework link state detection code use it in POLLING mode 3) fix 2 bugs in link state detection code: a) driver unable to detect link loss on bcm5721 b) on bcm570x chips (tested on bcm5700 bcm5701 bcm5702) driver fails to detect link loss with probability 1/6 (solved in brgphy.c) Devices working in TBI mode should not be affected by this change. Approved by:glebius (mentor) MFC after: 1 month Revision ChangesPath 1.102 +115 -105 src/sys/dev/bge/if_bge.c 1.38 +1 -1 src/sys/dev/mii/brgphy.c glebius 2005-12-08 16:11:45 UTC FreeBSD src repository Modified files: sys/dev/bge if_bge.c if_bgereg.h Log: A big rewrite of receive Jumbo frame handling. Remove the local Jumbo cluster allocator, that wasn't MPSAFE. Instead, utilize our new generic UMA jumbo cluster allocator. Since UMA gives us a 9k piece that is contigous in virtual memory, but isn't contigous in physical memory we need to handle a few segments. To deal with this we utilize Tigon chip feature - extended RX descriptors, that can handle up to four DMA segments for one frame. Details: o Remove bge_alloc_jumbo_mem(), bge_free_jumbo_mem(), bge_jalloc(), bge_jfree() functions. o Remove SLIST heads, bge_jumbo_tag, bge_jumbo_map from softc. o Use extended RX BDs for Jumbo receive producer ring, and initialize it appropriately. o New bge_newbuf_jumbo(): - Allocate an mbuf with Jumbo cluster with help of m_cljget(). - Load the cluster for DMA with help of bus_dmamap_load_mbuf_sg(). - Assert that we got 3 segments in the DMA mapping. - Fill in these 3 segments into the extended RX descriptor. Revision ChangesPath 1.103 +49 -233 src/sys/dev/bge/if_bge.c 1.39 +26 -15src/sys/dev/bge/if_bgereg.h marcel 2005-12-13 06:14:14 UTC FreeBSD src repository Modified files: sys/dev/bge if_bge.c Log: In bge_link_upd(), rewrite the logic so that status is assigned on the code path it is used in a way that GCC understands. This avoids breakage due to higher optimization levels. Revision ChangesPath 1.104 +2 -4 src/sys/dev/bge/if_bge.c yongari 2005-12-15 05:48:49 UTC FreeBSD src repository Modified files: sys/dev/bge if_bge.c if_bgereg.h Log: Add bge(4) support for big-endian architectures(part 1/2). - Give up endianess support and switch to native-endian
Re: FreeBSD 6.0-STABLE Totally Freezes on TightVNC Connection
It was some PCI 100MB card with an AMD chipset on it. Also, my connection is much faster now, so I suspect that the network card was going in the first place. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !!
Some change between Sun Nov 13 14:58:40 EET 2005 and Wed Jan 25 17:21:02 EET 2006 causes this message on boot: Jan 27 14:59:46 xx kernel: ad0: req=0xc306baf0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! Jan 27 14:59:47 xx kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=66763511 I have dma disabled on boot and /etc/rc.local enables it. Everything seem to be ok though, no problems with ad0 in DMA66. FreeBSD 6.0-STABLE (RELENG_6) [EMAIL PROTECTED]:4:0: class=0x0101fa card=0x80531043 chip=0x522910b9 rev=0xc4 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'M1543 Southbridge EIDE Controller' class= mass storage subclass = ATA ATA channel 0: Master: ad0 Maxtor 2F040L0/VAM51JJ0 ATA/ATAPI revision 7 Slave: no device present ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hi all.. Novice user having woes getting Atheros card up in FreeBSD 6.0
On Thursday 26 January 2006 08:10 pm, resonant evil wrote: Hi there.. So I can't use this wireless card at all right now? Damn why did I buy this thing then.. People from the mailing list showed me this one so I ordered it :-( All the posts on BSDForums.org list that the ath(4) driver in FreeBSD 6.0 only supports the AR5210, AR5211, and AR5212 chipset. It does not support the AR5213 which a lot of the newest Atheros-based cards are using. A quick search of the forums would have shown that. :) Similarly, the man page for ath(4) shows the three chipsets it supports. When buying wireless cards, the chipset is the only thing that matters. The name, model are irrelevent and often misleading. You have to search through the support/docs area of the manufacturer's website to find out exactly which chipset the card uses. This is horrible, I just spent a hundred bucks on something I can't even use? :( Update your system to RELENG_6 (6-STABLE) and apply the patches that Sam Leffler posts to http://people.freebsd.org/~sam That will allow you to use AR5213-based wireless NICs. I tested the patches on my laptop and they apply cleanly. I don't have any AR5213-based NICs to test with, though (all AR5212 at my house). I have instructions for getting the patches, applying the patches, and testing them. I'll send them to you via BSDForums (since that's where they're saved). -- Freddie Cash [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: How do I turn off hyperthreading on 6.0 ?
On Friday 27 January 2006 02:16 am, Pete French wrote: I though that machdep.hyperthreading_allowed had to be set to 1 to turn on hyperthreading ? I have a dual processor HP blade, and when I boot it up with an SMP kernel I get 4 CPU's. Setting that flag does not have any effect! Disable it in the BIOS. The kernel can't use what isn't advertised as available. :) -- Freddie Cash [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: Hi all.. Novice user having woes getting Atheros card up in FreeBSD 6.0
Yeah, someone told me about this exact card, I guess he figured it used Atheros so that meant it would work.. I wish I was so lucky. A nice fellow from Germany sent me an e-mail with a link to patching a file in the kernel, but I'm not sure how to do it.. But I guess I'll give it a try Does anyone else have any other advice for me here? Is there anything I can do or did I just purchase an absolute waste of money? Thanks guys On 1/27/06, Peter Jeremy [EMAIL PROTECTED] wrote: On Thu, 2006-Jan-26 20:10:56 -0800, resonant evil wrote: Hi there.. So I can't use this wireless card at all right now? Damn why did I buy this thing then.. People from the mailing list showed me this one so I ordered it :-( That exact card, or that model number? One major problem with PC hardware is that vendors regularly update the electronics without changing the model designations. This doesn't affect Windoze users because they provide updated drivers to match. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I turn off hyperthreading on 6.0 ?
Disable it in the BIOS. The kernel can't use what isn't advertised as available. :) true - but surely this is a bug in FreeBSD ? man smp says: Since using logical CPUs can cause performance penalties under certain loads, the logical CPUs can be disabled by setting the machdep.hlt_logical_cpus sysctl to one. I have: websvr04# sysctl machdep.hlt_logical_cpus machdep.hlt_logical_cpus: 1 but I am still seeing 4 CPU's as I have two physical processors, each with two logical ones onboard. I find it very hard to believe theres a bug in something this basic though, as it's specificly mentioned in the relase notes as being there to disable hyperthreading... very odd... -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I turn off hyperthreading on 6.0 ?
On Fri, Jan 27, 2006 at 07:24:06PM +, Pete French wrote: Disable it in the BIOS. The kernel can't use what isn't advertised as available. :) true - but surely this is a bug in FreeBSD ? man smp says: Since using logical CPUs can cause performance penalties under certain loads, the logical CPUs can be disabled by setting the machdep.hlt_logical_cpus sysctl to one. I have: websvr04# sysctl machdep.hlt_logical_cpus machdep.hlt_logical_cpus: 1 but I am still seeing 4 CPU's as I have two physical processors, each with two logical ones onboard. I find it very hard to believe theres a bug in something this basic though, as it's specificly mentioned in the relase notes as being there to disable hyperthreading... You misunderstand the point of this sysctl. All machdep.hlt_logical_cpus does is prevent anything from scheduling anything on the extra logical CPUs. Since nothing is scheduled on them, they don't contend with each other and the performance issues are mitigated. They are still there and there's nothing the OS can do about that. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpxfbf54DcW0.pgp Description: PGP signature
Re: How do I turn off hyperthreading on 6.0 ?
Pete French wrote: I have: websvr04# sysctl machdep.hlt_logical_cpus machdep.hlt_logical_cpus: 1 but I am still seeing 4 CPU's as I have two physical processors, each with two logical ones onboard. The way machdep.hlt_logical_cpus works is by telling the scheduler to ignore the extra logical processors, not by pretending that the extra logical processors don't exist at all. (This was necessary to ensure that interrupts could still run on the extra threads -- otherwise some problems appeared with broken BIOSes which couldn't route interrupts correctly.) If you look at top(1), which processors do you see actually running processes? Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I turn off hyperthreading on 6.0 ?
If you look at top(1), which processors do you see actually running processes? Errr, 0, 1, 2 and 3! That was my first clue that it hadn't worked as advertised! last pid: 2529; load averages: 0.53, 0.49, 0.34up 0+00:19:50 19:35:04 62 processes: 1 starting, 1 running, 60 sleeping CPU states: 1.4% user, 0.0% nice, 0.2% system, 0.1% interrupt, 98.3% idle Mem: 84M Active, 182M Inact, 135M Wired, 184K Cache, 112M Buf, 3111M Free Swap: 4096M Total, 4096M Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 1814 webadmin1 200 8016K 5972K lockf 1 0:01 0.10% httpd 717 root 11 960 76388K 57168K ucond 3 1:57 0.00% mysqld 723 webadmin1 200 8096K 6032K lockf 0 0:03 0.00% httpd 719 webadmin1 40 8104K 6052K sbwait 1 0:03 0.00% httpd 722 webadmin1 200 8100K 6024K lockf 0 0:03 0.00% httpd 721 webadmin1 40 8100K 6040K sbwait 2 0:03 0.00% httpd 718 webadmin1 40 8096K 6048K sbwait 2 0:03 0.00% httpd 735 webadmin1 40 8104K 6060K sbwait 2 0:03 0.00% httpd 736 webadmin1 200 8096K 6044K lockf 0 0:03 0.00% httpd 732 webadmin1 200 8096K 6044K lockf 0 0:03 0.00% httpd 935 webadmin1 40 8092K 6036K sbwait 2 0:03 0.00% httpd 720 webadmin1 200 8092K 6032K lockf 0 0:03 0.00% httpd 739 webadmin1 200 8232K 6164K lockf 3 0:03 0.00% httpd 724 webadmin1 40 8104K 6060K sbwait 0 0:02 0.00% httpd 733 webadmin1 40 8092K 6036K sbwait 1 0:02 0.00% httpd 737 webadmin1 960 8092K 6044K select 0 0:02 0.00% httpd 740 webadmin1 40 8092K 6052K sbwait 1 0:02 0.00% httpd ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I turn off hyperthreading on 6.0 ?
You misunderstand the point of this sysctl. All machdep.hlt_logical_cpus does is prevent anything from scheduling anything on the extra logical CPUs. Sadly I am seeing all 4 processors running httpd in top (see other email) -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hi all.. Novice user having woes getting Atheros card up in FreeBSD 6.0
Hi guys Here is where I am at now. Before we start, heres a DETAILED link to my exact wireless card: http://www.netgate.com/product_info.php?products_id=279 A nice guy named Eric from Germany e-mailed me with some information, saying to check out this website: http://lists.freebsd.org/pipermail/freebsd-mobile/2005-October/007243.html He thought that maybe the fix for his card might work for mine, but it doesn't appear to have.. Here is exactly what I did I copied that source code from http://sourceforge.net/mailarchive/message.php?msg_id=8966525 for the 'ar5k.c' file and compiled it. I then went to /usr/src/sys/dev/dev/ath and edited the 'if_ath.c' file. Correct me if I'm wrong but I was just supposed to change that one line of 'return EINVAL' to 'return 0' right? So I did that, saved it, and re-compiled the kernel fully, installed it, and rebooted, but I don't see even the slightest bit of info about the card still when the system boots up, and I definitely don't have an ath0 device still. Is there something like an 'lspci' command in Linux where I can get all the information from the card by probing it or whatever? FreeBSD can't detect this thing for the life of it :( Did I do anything wrong in those instructions? Is there anything I can do? Thanks :( On 1/27/06, resonant evil [EMAIL PROTECTED] wrote: Yeah, someone told me about this exact card, I guess he figured it used Atheros so that meant it would work.. I wish I was so lucky. A nice fellow from Germany sent me an e-mail with a link to patching a file in the kernel, but I'm not sure how to do it.. But I guess I'll give it a try Does anyone else have any other advice for me here? Is there anything I can do or did I just purchase an absolute waste of money? Thanks guys On 1/27/06, Peter Jeremy [EMAIL PROTECTED] wrote: On Thu, 2006-Jan-26 20:10:56 -0800, resonant evil wrote: Hi there.. So I can't use this wireless card at all right now? Damn why did I buy this thing then.. People from the mailing list showed me this one so I ordered it :-( That exact card, or that model number? One major problem with PC hardware is that vendors regularly update the electronics without changing the model designations. This doesn't affect Windoze users because they provide updated drivers to match. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I turn off hyperthreading on 6.0 ?
Pete French wrote: If you look at top(1), which processors do you see actually running processes? Errr, 0, 1, 2 and 3! What do # sysctl machdep.hlt_cpus # sysctl machdep.logical_cpus_mask # sysctl machdep.hyperthreading_allowed say? Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: manual escape to debugger on serial console not working?
On Jan 26, 2006, at 3:50 AM, Niki Denev wrote: i have this added to my kernel conf : options BREAK_TO_DEBUGGER options KDB options DDB I recommend ALT_BREAK_TO_DEBUGGER instead of BREAK_TO_DEBUGGER especially if you use cyclades terminal servers. They send BREAK on power-up so if you ever have to power cycle one you're gonna halt all of your other boxes.
Re: How do I turn off hyperthreading on 6.0 ?
What do # sysctl machdep.hlt_cpus # sysctl machdep.logical_cpus_mask # sysctl machdep.hyperthreading_allowed machdep.hlt_cpus: 10 machdep.logical_cpus_mask: 10 machdep.hyperthreading_allowed: 0 -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.0-STABLE Totally Freezes on TightVNC Connection
Er, more on that network card I said that screwed up the firewall, it's lnc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[5.4] mode bits changed by close(2)
I've found an interesting little quirk that doesn't seem like it
should be working this way. If I:
fd = open(file)
write(fd, data)
fchmod(fd, 04711) /* or anything set{u,g}id */
close(fd)
The set{u,g}id bits get cleared by the close, but only if the amount
of data is not a multiple of the page size, and the target file is on
an nfs mount. It would seem to reduce the utility of fchmod()
somewhat
A demonstration program is included below. I've verified this on a
fairly recently 5.4 client system, with both Linux and FBSD 5.4 NFS
servers. I don't have 6 or -current available to me at the moment.
There's the obvious work-around of doing a chmod() after the close,
but that has security implications.
Sticking an fsync() in between the fchmod() and the close() causes the
bits to be cleared as a side-effect of the fsync(). Doing another
fchmod() after the fsync() produces the final expected set{u,g}id
results even after the close. Unfortunately, fsync() is a rather
expensive operation.
Dworkin
#include stdio.h
#include stdlib.h
#include unistd.h
#include errno.h
#include string.h
#include fcntl.h
#include sys/types.h
#include sys/stat.h
char buf[25 * 1024];
int
main(int argc, char **argv)
{
int fd;
int count;
char *file;
struct stat sbuf;
if (argc != 2) {
fprintf(stderr, usage: %s /file/name\n, argv[0]);
exit(1);
}
file = argv[1];
fd = open(file, O_RDWR | O_CREAT, 0666);
if (fd == -1) {
fprintf(stderr, could not open %s: %s\n,
file, strerror(errno));
exit(1);
}
if (write(fd, buf, sizeof (buf)) == -1) {
fprintf(stderr, could not write to %s: %s\n,
file, strerror(errno));
exit(1);
}
if (fstat(fd, sbuf) == -1) {
fprintf(stderr, could not fstat %s: %s\n,
file, strerror(errno));
exit(1);
}
printf(Initial permissions: 0%o\n, sbuf.st_mode ALLPERMS);
if (fchmod(fd, 04711) == -1) {
fprintf(stderr, could not fchmod %s: %s\n,
file, strerror(errno));
exit(1);
}
if (fstat(fd, sbuf) == -1) {
fprintf(stderr, could not fstat %s: %s\n,
file, strerror(errno));
exit(1);
}
printf(After write: 0%o\n, sbuf.st_mode ALLPERMS);
if (close(fd) == -1) {
fprintf(stderr, could not close %s: %s\n,
file, strerror(errno));
exit(1);
}
if (stat(file, sbuf) == -1) {
fprintf(stderr, could not stat %s: %s\n,
file, strerror(errno));
exit(1);
}
printf(After close: 0%o\n, sbuf.st_mode ALLPERMS);
exit(0);
}
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
[danger] broken libc.so on stable
Revision 1.48.8.1 of lib/libc/stdlib/Makefile.inc removed calloc.c from the list of the source files. As result, freshly built libc does not contain calloc symbol, that completely broke my stable box. The only solution for me was booting from 6.0-RELEASE disc1 and copying libc.so.6 into /lib. After that, manually adding calloc.c to the MISRCS in Makefile.inc and installing libc put the system in order. I suppose that this is simple MFC error. Please, correct it before big havoc hit the stable boxes ! Best regards, Kostik Belousov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [5.4] mode bits changed by close(2)
On Saturday 28 January 2006 07:31, [EMAIL PROTECTED] wrote: A demonstration program is included below. I've verified this on a fairly recently 5.4 client system, with both Linux and FBSD 5.4 NFS servers. I don't have 6 or -current available to me at the moment. There's the obvious work-around of doing a chmod() after the close, but that has security implications. I tested it on a 6.0 server with a -current client.. [inchoate 8:55] /remotehome/darius ~/test ./foo Initial permissions: 0644 After write: 04711 After close: 0711 :( I also get the same result with a loopback NFS mount on -current. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpXBGy2IS1v1.pgp Description: PGP signature
Re: [danger] broken libc.so on stable
Kostik Belousov wrote: Revision 1.48.8.1 of lib/libc/stdlib/Makefile.inc removed calloc.c from the list of the source files. As result, freshly built libc does not contain calloc symbol, that completely broke my stable box. The only solution for me was booting from 6.0-RELEASE disc1 and copying libc.so.6 into /lib. After that, manually adding calloc.c to the MISRCS in Makefile.inc and installing libc put the system in order. I suppose that this is simple MFC error. Please, correct it before big havoc hit the stable boxes ! Best regards, Kostik Belousov Yes, there was a mistake for about 16 hours in the tree. However, how did you trash your system? Did you try building libc by itself and installing it directly? That's dangerous no matter what. Using the buildworld/installworld targets will catch problems like these before they touch your running system. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hi all.. Novice user having woes getting Atheros card up in FreeBSD 6.0
I think the newest D-link DWL-AG530 must use the AR5213 chipset too. Before I got it I had done some checking and read somewhere that it used the AR5212, so I thought I'd be ok. When I tried it recently I got: FreeBSD rock 6.0-STABLE FreeBSD 6.0-STABLE #1: Sun Jan 22 10:45:11 EST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/ROCK i386 ... ath0: Atheros 5212 mem 0xea00-0xea00 irq 11 at device 17.0 on pci0 ath0: unable to collect channel list from hal; regdomain likely 18 country code 0 device_attach: ath0 attach returned 22 I haven't tried Sam's patches yet. I'm assuming they're still current though. I have instructions for getting the patches, applying the patches, and testing them. I'll send them to you via BSDForums (since that's where they're saved). Can you point me to these instructions as well please? Yes, I already looked. :) -derek ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
undefined reference to calloc
Hello, In 6.0-STABLE when trying to build world i get a undefine refernce to calloc from libc.so right when it starts to build libexec/atrun but when i compile it stand alone it compiles fine same with libc but with the make buildworld var this error shows up sames place every time. Regards, Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: undefined reference to calloc
On Fri, Jan 27, 2006 at 08:57:26PM -0600, [EMAIL PROTECTED] wrote: Hello, In 6.0-STABLE when trying to build world i get a undefine refernce to calloc from libc.so right when it starts to build libexec/atrun but when i compile it stand alone it compiles fine same with libc but with the make buildworld var this error shows up sames place every time. This was fixed earlier today. Update and retry. Kris pgp5YzbdJPNft.pgp Description: PGP signature
Re: X.org 6.9 doesn't work with NVidia 7800 GTX (fwd)
I did get X.org running on 6-STABLE. As you have mentioned, starting X via X -probeonly with an Asus SLI motherboard and an NVidia 7800 GTX video card fails multiply; the internal configuration tries and fails to load module fbdev, meanwhile, the probe of the card dials the contrast of the syscons consoles down to near-zero levels. However, running Xorg -configure succeeds where the other fails. All modules are loaded, an x.conf file is written and the contrast is not blown. On my system, the monitor is able to support the highest resolution specified in the configuration file, though the text is unreadably small. Therefore, modulo tuning of the acceptable modes, X is now working on this configuration. Thanks for all your help! Mike O'Brien ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Make World Fails on Man Pages
Mark Andrews wrote: From unlink(2). [ENOTDIR] A component of the path prefix is not a directory. I suppose that is why rm is not working. The question was Why don't some man pages install? I think I have found the problem. Somewhere along the way a DOCSUPFILE make variable and separate doc-supfile came into existence. I never learned this so my doc sources were out of date. That gave me errors that caused me to set NO_SHARE which resulted in groff macros not being installed which resulted man page weirdness. This answer to myself for posterity. Later, Jason C. Wells ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
