From owner-freebsd-stable Sun Dec 23 0:38:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dart.sr.se (dart.sr.se [134.25.0.132]) by hub.freebsd.org (Postfix) with ESMTP id 83E4937B416 for ; Sun, 23 Dec 2001 00:38:04 -0800 (PST) Received: from honken.sr.se (honken.sr.se [134.25.128.27]) by dart.sr.se (8.11.6/8.11.6) with ESMTP id fBN8c0543099 for ; Sun, 23 Dec 2001 09:38:00 +0100 (CET) (envelope-from gunnar@pluto.sr.se) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.9.3/8.9.3) with ESMTP id JAA37276 for ; Sun, 23 Dec 2001 09:37:59 +0100 (CET) (envelope-from gunnar@pluto.sr.se) Received: (from root@localhost) by pluto.sr.se (8.11.6/8.11.1) id fBN8bxb76040 for freebsd-stable@freebsd.org; Sun, 23 Dec 2001 09:37:59 +0100 (CET) (envelope-from gunnar) Received: (from gunnar@localhost) by pluto.sr.se (8.11.6/8.11.1av) id fBN8bvN76032 for freebsd-stable@freebsd.org; Sun, 23 Dec 2001 09:37:57 +0100 (CET) (envelope-from gunnar) Date: Sun, 23 Dec 2001 09:37:56 +0100 From: Gunnar Flygt To: FreeBSD Stable Subject: Error on installworld Message-ID: <20011223093756.A75751@sr.se> Reply-To: Gunnar Flygt Mail-Followup-To: Gunnar Flygt , FreeBSD Stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I had a strange little error this morning, when `make installworld` failed when installing /usr/libexec/ld-elf.so.1 For some reason the old /usr/libexec/ld-elf.so.1.old was flagged schg so the renaming of the running one failed. Fixed it with a `chflags noschg`, but it made me slightly nervous for a short while. No big deal, but has anyone else experienced similar problems? -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 23 2: 2:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id B0B4437B419 for ; Sun, 23 Dec 2001 02:01:56 -0800 (PST) Received: from colt.ncptiddische.net (ppp-317.wobline.de [212.68.71.38]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fBNA1c816100; Sun, 23 Dec 2001 11:01:38 +0100 Received: from tisys.org (poison.ncptiddische.net [192.168.0.5]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fBNA3YX50115; Sun, 23 Dec 2001 11:03:35 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id fBNA26k01450; Sun, 23 Dec 2001 11:02:06 +0100 (CET) (envelope-from nils) Date: Sun, 23 Dec 2001 11:01:30 +0100 From: Nils Holland To: Matthew Dillon Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS problems in 4.5-PRERELEASE Message-ID: <20011223110130.B1269@tisys.org> Mail-Followup-To: Matthew Dillon , freebsd-stable@FreeBSD.ORG References: <20011223005213.A57692@tisys.org> <200112230459.fBN4x0u99894@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112230459.fBN4x0u99894@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Dec 22, 2001 at 08:59:00PM -0800 X-Operating-System: FreeBSD poison.ncptiddische.net 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE X-Machine-Uptime: 10:42AM up 16 mins, 1 user, load averages: 0.04, 0.01, 0.00 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Dec 22, 2001 at 08:59:00PM -0800, Matthew Dillon stood up and spoke: > > This kinda sounds like a memory allocation failure in the kernel, > perhaps the kernel is running out of KVM. I have a couple of > recommendations and questions. > > * post your kernel config > * post your /var/run/dmesg.boot output I've started looking at the problem again, and the interesting thing is that I have now tarred up /japanese/mnews and deleted the directory, which makes my ports tree copy fine. I'll try again, and then untar mnews again and see what happens. I don't have a clue what the japanese mnews port should have to do with causing this problem... Oh, here is my kernel config and dmesg boot: -> # # JODIE -- Ti Systems kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.35 2001/09/27 17:43:06 alfred Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident JODIE maxusers 0 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support #options MFS #Memory Filesystem #options MD_ROOT #MD is a potential root device options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required #options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device fd1 at fdc0 drive 1 # # If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy, # don't use the above line for fdc0 but the following one: #device fdc0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals #device scbus # SCSI bus (required) #device da # Direct Access (disks) #device sa # Sequential Access (tape etc) #device cd # CD #device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache - See LINT for options! #device mly # Mylex AcceleRAID/eXtremeRAID # RAID controllers #device aac # Adaptec FSA RAID, Dell PERC2/PERC3 #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family #device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support #device card #device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 #device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports #device sio0 at isa? port IO_COM1 flags 0x10 irq 4 #device sio1 at isa? port IO_COM2 irq 3 #device sio2 at isa? disable port IO_COM3 irq 5 #device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer #device plip # TCP/IP over parallel #device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') #device txp # 3Com 3cR990 (``Typhoon'') #device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device pcn # AMD Am79C97x PCI 10/100 NICs #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device ste # Sundance ST201 (D-Link DFE-550TX) #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device wx # Intel Gigabit Ethernet Card (``Wiseman'') #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. # 'device ed' requires 'device miibus' device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ex #device ep #device fe0 at isa? port 0x300 # Xircom Ethernet #device xe # PRISM I IEEE 802.11b wireless NIC. #device awi # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attachment needed # and resources will always be dynamically assigned by the pccard code. #device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those parameters here. #device an # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) #pseudo-device md # Memory "disks" pseudo-device gif # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support #device uhci # UHCI PCI->USB interface #device ohci # OHCI PCI->USB interface #device usb # USB Bus (required) #device ugen # Generic #device uhid # "Human Interface Devices" #device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da #device ums # Mouse #device uscanner # Scanners #device urio # Diamond Rio MP3 Player # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet # More Added Stuff device pcm options SC_DISABLE_REBOOT pseudo-device vn options UFS_DIRHASH --> (dmesg.boot (This is actually boot -v because I booted that way with the hope of probably finding some helpful information this way...) Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-PRERELEASE #0: Sat Dec 22 10:04:01 CET 2001 root@poison.ncptiddische.net:/usr/obj/usr/src/sys/JODIE Calibrating clock(s) ... TSC clock: 996730453 Hz, i8254 clock: 1193305 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 996633681 Hz CPU: AMD Athlon(tm) processor (996.63-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> Data TLB: 24 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 805240832 (786368K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00385000 - 0x2ffe7fff, 801517568 bytes (195683 pages) avail memory = 779407360 (761140K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fad80 bios32: Entry = 0xfb1f0 (c00fb1f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb220 pnpbios: Found PnP BIOS data at 0xc00fbce0 pnpbios: Entry = f0000:bd10 Rev = 1.0 Other BIOS signatures found: ACPI: 000f79d0 Preloaded elf kernel "kernel" at 0xc035e000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 pci_open(1): mode 1 addr port (0x0cf8) is 0x80003840 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=03051106) Using $PIR table, 8 entries at 0xc00fdba0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard found-> vendor=0x1106, dev=0x0305, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base d0000000, size 27 found-> vendor=0x1106, dev=0x8305, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x1106, dev=0x0686, revid=0x40 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1106, dev=0x0571, revid=0x06 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000d000, size 4 found-> vendor=0x1106, dev=0x3038, revid=0x16 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=5 map[20]: type 1, range 32, base 0000d400, size 5 found-> vendor=0x1106, dev=0x3038, revid=0x16 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=5 map[20]: type 1, range 32, base 0000d800, size 5 found-> vendor=0x1106, dev=0x3057, revid=0x40 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1106, dev=0x3058, revid=0x50 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=c, irq=10 map[10]: type 1, range 32, base 0000dc00, size 8 map[14]: type 1, range 32, base 0000e000, size 2 map[18]: type 1, range 32, base 0000e400, size 2 found-> vendor=0x10ec, dev=0x8029, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 0000e800, size 5 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x1002, dev=0x474d, revid=0x27 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base d8000000, size 24 map[14]: type 1, range 32, base 0000c000, size 8 map[18]: type 1, range 32, base da000000, size 12 pci1: on pcib1 pci1: (vendor=0x1002, dev=0x474d) at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI probe a=00 b=00 ata0-slave: ATAPI probe a=00 b=00 ata0: mask=03 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd008 ata1: mask=03 status0=50 status1=50 ata1: mask=03 ostat0=50 ostat2=50 ata1-master: ATAPI probe a=14 b=eb ata1-slave: ATAPI probe a=14 b=eb ata1: mask=03 status0=10 status1=00 ata1: devices=0c ata1: at 0x170 irq 15 on atapci0 pci0: (vendor=0x1106, dev=0x3038) at 7.2 irq 5 pci0: (vendor=0x1106, dev=0x3038) at 7.3 irq 5 chip1: at device 7.4 on pci0 pcm0: port 0xe400-0xe403,0xe000-0xe003,0xdc00-0xdcff irq 10 at device 7.5 on pci0 pcm0: ac97 codec id 0x83847609 (SigmaTel STAC9721/9723) pcm0: ac97 codec features 18 bit DAC, 18 bit ADC, 5 bit master volume, SigmaTel 3D Enhancement pcm0: ac97 primary codec extended features AMAP pcm: setmap 2e9d0000, 1000; 0xc307c000 -> 2e9d0000 pcm: setmap 2e9f2000, 1000; 0xc307e000 -> 2e9f2000 ed0: port 0xe800-0xe81f irq 11 at device 17.0 on pci0 bpf: ed0 attached ed0: address 00:20:18:2f:42:2d, type NE2000 (16 bit) ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number ed-: ed0 exists, using next available unit number Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0:
auto is not reliable ( at least for the fxp driver ).  It always succeeds when I force full duplex though.


"Keith J" <kjohnso8@columbus.rr.com>
Sent by: owner-freebsd-stable@FreeBSD.ORG

12/26/2001 12:46 AM

       
        To:        "Tom" <tom@uniserve.com>
        cc:        "Peter Ong" <peter@haloflightleader.net>, "Robert Watson" <rwatson@FreeBSD.ORG>, "Nevermind" <never@nevermind.kiev.ua>, "Murray Stokely" <murray@FreeBSD.ORG>, <stable@FreeBSD.ORG>, <freebsd-qa@FreeBSD.ORG>, <bmah@FreeBSD.ORG>
        Subject:        Re: 4.5 PRERELEASE - Call for testing


Well gee Tom.... if one end doesn't respond to negotiation... are you saying
the smart end will force a speed or duplex that can't possibly work? Lets
say I have an old 10Mbs ONLY card... are you declaring that it gets toasted
by auto-negotiate every single time?

It is well known that a major issue existed with some NIC's and switches a
few years back because the initial standards were not explicit enough. Some
in the industry took the directives to mean one thing, and others to be
different enough that "auto" was not reliable. Given that many FreeBSD users
collect hardware from a few years past, I applied this reasoning as a
possible culprit. I also mentioned several others, but you saw fit to remove
them... evidently to make your point about "todays state" of hardware.

If you want to call something "bad advice" please be specific as to the
aspects and why that is so... I find people that edit responses and then
hold court while passing judgement with blanket and terse responses to be
rather tiresome and out of character with the ideal of a free exchange of
knowledge. Bottom line, I have yet to see an expensive smart switch or
inexpensive switch insist on a 10/100 mode that could not be supported when
one end was "locked down". If this is not the case for you, please enlighten
us all with your "personal" real world experience.

On the other hand, if this is an issue with the semantics of auto-detect vs
auto-negotiate... well, I can't help it if industry can't be consistent in
their documentation. Perhaps I am going over the presumption line here...
but I don't think most home users here are people running trunking using
dot1q or Cisco isl to get their Mp3's... and for the record... even if one
"auto-detects" something as simple as 10/100 it still must "negotiate" the
balance of parameters, given that human intervention is not required...
hence it is defacto "automatic", and thus my characterization as
"auto-negotiate".

As far as trunking goes... auto-negotiate trunking doesn't necessarily tell
one what it finally settled on, or that it even settled on something.... and
is a whole other thread entirely.

It is always better to be parameter specific, and to that extent I do agree
with you - if one can explicitly lock down both ends so much the better, but
not all inexpensive switches can.... and my experience has told me it isn't
necessary.

Keith

----- Original Message -----
From: "Tom" <tom@uniserve.com>
To: "Keith J" <kjohnso8@columbus.rr.com>
Cc: "Peter Ong" <peter@haloflightleader.net>; "Robert Watson"
<rwatson@FreeBSD.ORG>; "Nevermind" <never@nevermind.kiev.ua>; "Murray
Stokely" <murray@FreeBSD.ORG>; <stable@FreeBSD.ORG>;
<freebsd-qa@FreeBSD.ORG>; <bmah@FreeBSD.ORG>
Sent: Tuesday, December 25, 2001 1:50 PM
Subject: Re: 4.5 PRERELEASE - Call for testing


>
> On Tue, 25 Dec 2001, Keith J wrote:
>
> ...
> > Another possibility is you do not have a Samba problem, but a network
> > problem with auto-negotiate. Some older 10/100 cards and switch
combinations
> > step all over each other. You should lock down one end to a specific
speed
> ...
>
>   That is bad advice.  Auto-negotiation is not auto-detect.  If you
> disable auto-negotiate at one end and specify manual settings, you must
> disable it on the other end too, and specify the SAME manual settings.
> Either use auto-negotiate everywhere, or use manual everywhere.  I would
> recommend using auto everywhere.
>
> Tom
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message

--=_alternative 0035A0E788256B2E_=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 4: 8:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 5F4C037B405 for ; Wed, 26 Dec 2001 04:08:24 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBQC8EI13129; Wed, 26 Dec 2001 13:08:14 +0100 (CET) (envelope-from wkb) Date: Wed, 26 Dec 2001 13:08:14 +0100 From: Wilko Bulte To: sthaug@nethelp.no Cc: kjohnso8@columbus.rr.com, stable@FreeBSD.ORG Subject: Re: 4.5 PRERELEASE - Call for testing Message-ID: <20011226130814.A13115@freebie.xs4all.nl> References: <001301c18de9$c7ed5240$3602a8c0@columbus.rr.com> <97595.1009359920@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <97595.1009359920@verdi.nethelp.no>; from sthaug@nethelp.no on Wed, Dec 26, 2001 at 10:45:20AM +0100 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 26, 2001 at 10:45:20AM +0100, sthaug@nethelp.no wrote: > > Well gee Tom.... if one end doesn't respond to negotiation... are you saying > > the smart end will force a speed or duplex that can't possibly work? Lets > > say I have an old 10Mbs ONLY card... are you declaring that it gets toasted > > by auto-negotiate every single time? > > It's very simple. The devices at each end of a TP cable can autodetect > speed. However, if the duplex mode is locked (set manually) at one end > (whether it is locked at half or full duplex), you *cannot* depend on > the other end to get the correct duplex mode. Sometimes it will work, > sometimes it won't. > > Thus the advice to either use auto-negotiate everywhere, or use manual > everywhere. One end auto-negotiate and one end manual is a recipe for > disaster. So, that implies that in these cases non-managable switches are doomed as you cannot 'hard-set' them to some value. -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 5: 0:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 54BBB37B417 for ; Wed, 26 Dec 2001 05:00:30 -0800 (PST) Received: (qmail 99529 invoked by uid 1001); 26 Dec 2001 13:00:27 +0000 (GMT) To: wkb@freebie.xs4all.nl Cc: stable@FreeBSD.ORG Subject: Re: 4.5 PRERELEASE - Call for testing From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 26 Dec 2001 13:08:14 +0100" References: <20011226130814.A13115@freebie.xs4all.nl> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 26 Dec 2001 14:00:27 +0100 Message-ID: <99527.1009371627@verdi.nethelp.no> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Thus the advice to either use auto-negotiate everywhere, or use manual > > everywhere. One end auto-negotiate and one end manual is a recipe for > > disaster. > > So, that implies that in these cases non-managable switches are doomed > as you cannot 'hard-set' them to some value. If auto-negotiate fails on non-managable switches, you can usually get it to work after the fact by manually configuring the box at the other end. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 5: 2:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from empty1.ekahuna.com (empty1.ekahuna.com [198.144.200.196]) by hub.freebsd.org (Postfix) with ESMTP id 86F1C37B416 for ; Wed, 26 Dec 2001 05:02:07 -0800 (PST) Received: from pc-02 (pc02.ekahuna.com [198.144.200.197]) by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Wed, 26 Dec 2001 05:02:06 -0800 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: stable@FreeBSD.ORG Date: Wed, 26 Dec 2001 05:02:06 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Bind 9 and FreeBSD-Stable? Reply-To: pjklist@ekahuna.com Message-ID: <3C2959CE.30460.1BFF136@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Are there any plans to switch to Bind 9 as the standard BIND release in FreeBSD any time soon? I note that 4.4-Release is still using 8.2.4, and since I haven't updated my sources for quite a while so I'm not sure if that has changed any. But given that BIND started out as the "Berkeley Internet Name Daemon", and that AFAIK much of its development still occurs on FreeBSD, doesn't it make sense to move in that direction since v9 seems to be fairly well-accepted these days? I've gotten stuck with multiple versions of BIND in FreeBSD before and I'd much rather just use the stuff that's part of the base distribution as it's more foolproof to update and keep track of. Thanks, Phil -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 5:45:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail8.sdc1.sfba.home.com (femail8.sdc1.sfba.home.com [24.0.95.88]) by hub.freebsd.org (Postfix) with ESMTP id 9F0C837B405 for ; Wed, 26 Dec 2001 05:45:50 -0800 (PST) Received: from crazyhorse ([24.21.114.209]) by femail8.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20011226134545.OSXX16621.femail8.sdc1.sfba.home.com@crazyhorse> for ; Wed, 26 Dec 2001 05:45:45 -0800 Message-Id: <3.0.5.32.20011226064544.0095fa00@mail.tucson1.az.home.com> X-Sender: rpsbsd@mail.tucson1.az.home.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 26 Dec 2001 06:45:44 To: freebsd-stable@freebsd.org From: R Paschal Subject: Re: 4.5-PRERELEASE announcement ? In-Reply-To: References: <20011225205928.C29819@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 11:29 PM 12/25/01 -0500, Robert Watson wrote: >General project release schedule announcements have been going to >freebsd-announce, I believe, but the nitty-gritty posts relating to the >details of a particular release cycle probably belong on lists for the >more generally dedicated. It may be that an announcement of the sort: Can the general project release announcements be posted into the newsgroup comp.unix.bsd.freebsd.announce? The only thing that I've seen posted there for a long time is the new ports added/updated by Wolfram Schneider. Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 5:47:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 368A137B41E; Wed, 26 Dec 2001 05:47:46 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id fBQDgrl62416; Wed, 26 Dec 2001 05:42:53 -0800 (PST) (envelope-from rizzo) Date: Wed, 26 Dec 2001 05:42:53 -0800 From: Luigi Rizzo To: "Robert D. Hughes" Cc: Yusuf Goolamabbas , freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, cez@pkl.net Subject: Re: 4.4-stable kernel panic with dummynet/bridging. Same rules work fine with 4.3-RC Message-ID: <20011226054253.A62387@iguana.aciri.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have found the bug, it's a one-line change in netinet/if_ether.c @@ -574,5 +574,4 @@ in_arpinput(m) m_freem(m); return; } - ia = ifatoia(ifa); match: I am waiting for re@ to approve the commit. The code in -current is already fixed. cheers luigi On Thu, Dec 20, 2001 at 08:27:58AM -0600, Robert D. Hughes wrote: > Hmmmm.... I thought it was just me, and I hadn't had a chance yet to go > digging. I just enabled OPTIONS = BRIDGE in the kernel and I was getting > spontaneous reboots, but they pointed to NATD blowing up. Essentially > the same error though. Removing OPTIONS = BRIDGE seems to have stopped > the reboots. This is on the 4.4-STABLE tree and has been going on for at > least a couple of weeks. > > Rob > > -----Original Message----- > From: Yusuf Goolamabbas [mailto:yusufg@outblaze.com] > Sent: Thursday, December 20, 2001 5:16 AM > To: freebsd-net@freebsd.org; freebsd-stable@freebsd.org > Cc: cez@pkl.net > Subject: 4.4-stable kernel panic with dummynet/bridging. Same rules work > fine with 4.3-RC > > > Hi, Similar to what Ceri describes in this message > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=508422+0+current/freebsd-st > able > > I have observed a 4.4-stable box panicing whenever bridging is turned > on. This was cvsup'ed today morning. I have other boxes cvsup'ed at > the same time except that they don't have dummynet/bridging configured > in them and they work pretty well > > I replaced the box with an another 4.3-RC box and the same rules > enclosed here work just fine > > ${fwcmd} add 100 pass all from any to any via lo0 > ${fwcmd} add 200 deny all from any to 127.0.0.0/8 > ${fwcmd} add 300 deny ip from 127.0.0.0/8 to any > # If you're using 'options BRIDGE', uncomment the following line to pass > ARP > ${fwcmd} add 400 pass udp from 0.0.0.0 2054 to 0.0.0.0 > ${fwcmd} add 500 pass all from to any in via fxp0 > ${fwcmd} add 800 pipe 1 ip from to any in via fxp1 > ${fwcmd} pipe 1 config mask src-ip 0x000000ff bw 512Kbit/s queue 50 > > Basically, fxp1 is connected to a switch and every machine on that > switch is rate limited to 512Kbit/s individually > > I had configured the box with DDB but didn't have serial console so I > transcribed everything at the db> prompt > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xa4 > fault code = superviser read, page not present > instruction pointer = 0x8:0xc0199164 > strack pointer = 0x10:0xc9889b5c > frame pointer = 0x10:0xc9889bac > code segment = base 0x0, limit 0xfff type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 55 (sh) > interrupt mask = > kernel: type 12 trap, code = 0 > stopped at in_arpinput+0x158; movl 0xa4(%eax,%eax) > > db> t > in_arpinput(c077cb00,0,c989cac,c020d625,c020d5df) at in_arpinput+0x158 > arpintr(c020dfdf,0,c02800,0,c7640010,c0e700,0) at arpintr+0x112 > swi_net_next(c028c26c,c764f000,3,0,c835c440) at swi_net_next > trap_pfault(c9889d20,0,c764f000,0,806c591) at trap_pfault+0xbe > trap(10,c9880010,c01d0010,c764f000,80be591_ at trap+0x31f > calltrap() at calltrap+0x11 > trap 0xc : eip - 0xc02172cf , esp - 0xc9889d60, ebp - 0xc9889d88 > copyinstr(c9889e68,0,0,c9889f80,c9889f80) at copyinstr+0x37 > exec_elf_imagact(c9889e68,c835c440,3,c9889f80,c9889e68) at > exec_elf_imagact+0xba > execve(c835c440,c9889f80,80be5d4,0,80be590) at execve+0x26c > syscall2(2f,2f,2f,80be590,0) at syscall2+0x1a5 > Xinit0x80_syscall() + Xint-x80_syscall+0x25 > > Hope this helps > > Regards, Yusuf > > -- > Yusuf Goolamabbas > yusufg@outblaze.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 6: 1:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hugo10.ka.punkt.de (kagate.punkt.de [194.77.232.254]) by hub.freebsd.org (Postfix) with ESMTP id 652DC37B416 for ; Wed, 26 Dec 2001 06:01:49 -0800 (PST) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.11.4/8.11.4) id fBQE1hb47452 for freebsd-stable@freebsd.org; Wed, 26 Dec 2001 15:01:43 +0100 (CET) (envelope-from ry93) From: "Patrick M. Hausen" Message-Id: <200112261401.fBQE1hb47452@hugo10.ka.punkt.de> Subject: RELENG_4_5 To: freebsd-stable@freebsd.org Date: Wed, 26 Dec 2001 15:01:43 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL92 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello all! Just a minor question: at which point in the 4.5 release cycle will a RELENG_4_5 tag appear? I'd be more than happy to test -PRERELEASE and/or -BETA on a couple of machines, but I'd rather change my cvsupfiles from RELENG_4_4 to RELENG_4_5 than RELENG_4. Saves me from changing them back after -RELEASE. Wouldn't it make sense if -BETAs and -RCs were already tagged RELENG_4_X? Regards, Patrick M. Hausen Technical Director -- punkt.de GmbH Internet - Dienstleistungen - Beratung Scheffelstr. 17 a Tel. 0721 9109 -0 Fax: -100 76135 Karlsruhe http://punkt.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 6:13:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id B1B9B37B41A for ; Wed, 26 Dec 2001 06:13:34 -0800 (PST) Received: (qmail 7576 invoked by uid 0); 26 Dec 2001 14:13:33 -0000 Received: from pd950884a.dip.t-dialin.net (HELO mail.gsinet.sittig.org) (217.80.136.74) by mail.gmx.net (mp006-rz3) with SMTP; 26 Dec 2001 14:13:33 -0000 Received: (qmail 53080 invoked from network); 26 Dec 2001 13:46:27 -0000 Received: from shell.gsinet.sittig.org (192.168.11.153) by mail.gsinet.sittig.org with SMTP; 26 Dec 2001 13:46:27 -0000 Received: (from sittig@localhost) by shell.gsinet.sittig.org (8.11.3/8.11.3) id fBQDkIW53067 for freebsd-stable@freebsd.org; Wed, 26 Dec 2001 14:46:18 +0100 (CET) (envelope-from sittig) Date: Wed, 26 Dec 2001 14:46:17 +0100 From: Gerhard Sittig To: freebsd-stable@freebsd.org Subject: Re: 4.5 PRERELEASE - Call for testing Message-ID: <20011226144617.P1494@shell.gsinet.sittig.org> Mail-Followup-To: freebsd-stable@freebsd.org References: <05ae01c18d80$df7bfe20$0a05a8c0@ooe.kmjeuro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <05ae01c18d80$df7bfe20$0a05a8c0@ooe.kmjeuro.com>; from k.joch@kmjeuro.com on Tue, Dec 25, 2001 at 09:15:10PM +0100 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Dec 25, 2001 at 21:15 +0100, Karl M. Joch wrote: > > i would like to get my notebook,which hangs on boot (pcic), to run again > with freebsd. was there any recent changes or any hints how i could get > around that problem? (the problem was posted with KAPOK in the subject). You didn't state (again) where it "hangs on boot". Plus I didn't feel like crawling the archives again (BTW Message-Id's are far better handles than single words in the subject line). Is your problem by any chance the famous(?) hw.pcic.intr_path=1 hw.pcic.irq=0 thingy? If these settings help you at boot time, just put them into your /boot/loader.conf and things should keep working. These settings are not in UPDATING as I can see, but Warner Losh posted quite a few of these instructions again and again into the lists (both -stable and -mobile). And these lines might be in the 4.4 RELNOTES, too (don't have them handy ATM). For your searching here's the initial announcement, while many people asked this question again and got answered, too. :) Message-Id: <200108260507.f7Q570W08734@harmony.village.org> From: Warner Losh To: mobile@freebsd.org Cc: doc@freebsd.org Date: Sat, 25 Aug 2001 23:06:59 -0600 Subject: MFC: ISA routing support virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 6:14:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 8F96137B416 for ; Wed, 26 Dec 2001 06:14:00 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBQEDv613735; Wed, 26 Dec 2001 15:13:57 +0100 (CET) (envelope-from wkb) Date: Wed, 26 Dec 2001 15:13:57 +0100 From: Wilko Bulte To: "Patrick M. Hausen" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: RELENG_4_5 Message-ID: <20011226151357.A13721@freebie.xs4all.nl> References: <200112261401.fBQE1hb47452@hugo10.ka.punkt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112261401.fBQE1hb47452@hugo10.ka.punkt.de>; from hausen@punkt.de on Wed, Dec 26, 2001 at 03:01:43PM +0100 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 26, 2001 at 03:01:43PM +0100, Patrick M. Hausen wrote: > Hello all! > > Just a minor question: at which point in the 4.5 release cycle > will a RELENG_4_5 tag appear? I'd be more than happy to test > -PRERELEASE and/or -BETA on a couple of machines, but I'd rather > change my cvsupfiles from RELENG_4_4 to RELENG_4_5 than RELENG_4. > Saves me from changing them back after -RELEASE. RELENG_4_5 == 4.5RELEASE -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 6:39:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from spock.webexc.com (zzz-216043142149.splitrock.net [216.43.142.149]) by hub.freebsd.org (Postfix) with ESMTP id E216B37B41B for ; Wed, 26 Dec 2001 06:39:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by spock.webexc.com (Postfix) with ESMTP id ABBD6B7 for ; Wed, 26 Dec 2001 09:41:30 -0500 (EST) Date: Wed, 26 Dec 2001 09:41:30 -0500 (EST) From: Matt Barton X-X-Sender: mbarton@spock.webexc.com To: stable@freebsd.org Subject: Re: Bind 9 and FreeBSD-Stable? In-Reply-To: <3C2959CE.30460.1BFF136@localhost> Message-ID: <20011226092242.Q27780-100000@spock.webexc.com> Organization: Webexcellence MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 26 Dec 2001, Philip J. Koenig wrote: > Are there any plans to switch to Bind 9 as the standard BIND release in > FreeBSD any time soon? > > I note that 4.4-Release is still using 8.2.4, and since I haven't > updated my sources for quite a while so I'm not sure if that has changed > any. > > But given that BIND started out as the "Berkeley Internet Name Daemon", > and that AFAIK much of its development still occurs on FreeBSD, doesn't > it make sense to move in that direction since v9 seems to be fairly > well-accepted these days? > > I've gotten stuck with multiple versions of BIND in FreeBSD before and > I'd much rather just use the stuff that's part of the base distribution > as it's more foolproof to update and keep track of. My gut tells me that it'll be a while before the default FreeBSD version of BIND is version 9. There are many programs out there, as I understand, that are incompatible with it, whereas they work fine with version 8. One such application I know, for fact, that doesn't work with BIND 9 is Lyris ListManagerSQL. We have a customer of our running it one Windows 2000 and Lyris specifically told them not to configure the software to query a BIND 9 server. Works perfectly find with BIND 8. I think this is more of a problem with Lyris than with BIND, but I am guessing that we will have to wait for software developers to fix their software before FreeBSD dares to switch BIND versions. I have had no problems using the BIND 9 port and have been able to run it without any conflicts. I simply run everything within /usr/local instead and disable the binaries for BIND 8. I also disable the making of BIND 8 in my /etc/make.conf file. -- Matt Barton Webexcellence matt@webexc.com Phone: 317.423.3548 x22 Fax: 317.423.8735 www.webexc.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 6:47:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emmi.physik.TU-Berlin.DE (emmi.physik.TU-Berlin.DE [130.149.160.103]) by hub.freebsd.org (Postfix) with ESMTP id 0C3C237B417 for ; Wed, 26 Dec 2001 06:47:51 -0800 (PST) Received: (from ibex@localhost) by emmi.physik.TU-Berlin.DE (8.11.6/8.11.6) id fBQElmR12235; Wed, 26 Dec 2001 15:47:48 +0100 (CET) (envelope-from ibex) Date: Wed, 26 Dec 2001 15:47:48 +0100 From: Dirk Froemberg To: Wilko Bulte Cc: "Patrick M. Hausen" , freebsd-stable@freebsd.org Subject: Re: RELENG_4_5 Message-ID: <20011226154748.A11930@physik.TU-Berlin.DE> References: <200112261401.fBQE1hb47452@hugo10.ka.punkt.de> <20011226151357.A13721@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011226151357.A13721@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Wed, Dec 26, 2001 at 03:13:57PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! On Wed, Dec 26, 2001 at 03:13:57PM +0100, Wilko Bulte wrote: > On Wed, Dec 26, 2001 at 03:01:43PM +0100, Patrick M. Hausen wrote: > > Just a minor question: at which point in the 4.5 release cycle > > will a RELENG_4_5 tag appear? I'd be more than happy to test > > -PRERELEASE and/or -BETA on a couple of machines, but I'd rather > > change my cvsupfiles from RELENG_4_4 to RELENG_4_5 than RELENG_4. > > Saves me from changing them back after -RELEASE. > > RELENG_4_5 == 4.5RELEASE Hmm, not quite: RELENG_4_5_0_RELEASE == 4.5-RELEASE 8-) I think, Patrick refers to the RELENG_4_5 branch similar to RELENG_4_4 and RELENG_4_3. Probably RELENG_4_5 will appear not before 4.5-RELEASE. But in the end it's up to the release engineer. Regards Dirk -- Dirk Froemberg FreeBSD: The Power to Serve! http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 6:53:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [66.31.234.148]) by hub.freebsd.org (Postfix) with ESMTP id 5938337B42C for ; Wed, 26 Dec 2001 06:53:19 -0800 (PST) Received: (from root@localhost) by thehousleys.net (8.11.6/8.11.2) id fBQErIq84976; Wed, 26 Dec 2001 09:53:18 -0500 (EST) (envelope-from jim@Thehousleys.net) Received: from Thehousleys.net (baby.int.thehousleys.net [192.168.0.24]) (authenticated) by thehousleys.net (8.11.6/8.11.6) with ESMTP id fBQEr8u84968; Wed, 26 Dec 2001 09:53:08 -0500 (EST) (envelope-from jim@Thehousleys.net) Message-ID: <3C29E453.4179E2FB@Thehousleys.net> Date: Wed, 26 Dec 2001 09:53:07 -0500 From: James Housley X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ollivier Robert Cc: stable@freebsd.org Subject: Re: NTPD dumps core in 4.5-PRERELEASE References: <3C269EE2.7820ACBC@Thehousleys.net> <20011225195642.B711@tara.freenix.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ollivier Robert wrote: > > According to James Housley: > > 12/22 5am EST. 1 CVSup 12/23 5am EST. The laptop is dumps core on > > startup only with 12/22 & 12/23. I don't believe this was doing this > > before 4.1.0. If I re-run with the exact same parameters after the boot > > is finished all is well. Attached is the dmesg.boot and some debug > > information from the core file. This is reproduceable with every reboot > > on this one machine. > > When you boot this machine, do you have access to the IP addresses of all your > ntp.conf servers/peers ? > > > 1553 if (!peer->reach || (peer->stratum > 1 && > > 1554 peer->refid == > > (gdb) > > 1555 peer->dstadr->sin.sin_addr.s_addr) || > > 1556 peer->stratum >= STRATUM_UNSPEC || > > 1557 (root_distance(peer) >= MAXDISTANCE + 2 * > > 1558 clock_phi * ULOGTOD(sys_poll))) > ... > > (gdb) p peer > > $1 = (struct peer *) 0x80829a8 > > (gdb) p (struct peer *) peer > > $2 = (struct peer *) 0x80829a8 > > (gdb) p *(struct peer *) peer > > $3 = {next = 0x0, ass_next = 0x0, srcadr = {sin_len = 0 '\000', > > sin_family = 2 '\002', sin_port = 31488, sin_addr = {s_addr = 98175}, > > sin_zero = "\000\000\000\000\000\000\000"}, dstadr = 0x0, associd = 59212, > > It is pretty obvious that your problem is that dstadr is NULL so > peer->dstadr->whatever will segfault. > I am not sure why this is so. I have local DNS running on my router and another machine. Besides the laptop, three other machines are using the same peers. So the IP should be in the DNS. I agree that there is a NULL pointer here, but isn't this some thing that should be checked for in the program? And as mentioned in the origional post: If I rerun the program after startup and it has segfaulted, it has never segfaulted again. This also started after the 4.1.0 upgrade. Thanks for you help. Jim -- /"\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ ----------------------------------------------------------------- jeh@FreeBSD.org http://www.FreeBSD.org The Power to Serve jim@TheHousleys.Net http://www.TheHousleys.net jhousley@SimTel.Net http://www.SimTel.Net --------------------------------------------------------------------- Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 7:23:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id D487D37B405 for ; Wed, 26 Dec 2001 07:23:07 -0800 (PST) Received: from colt.ncptiddische.net (ppp-179.wobline.de [212.68.69.187]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fBQFMN825862; Wed, 26 Dec 2001 16:22:28 +0100 Received: from tisys.org (poison.ncptiddische.net [192.168.0.5]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fBQFMBX69476; Wed, 26 Dec 2001 16:22:12 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id fBQFMAu02631; Wed, 26 Dec 2001 16:22:10 +0100 (CET) (envelope-from nils) Date: Wed, 26 Dec 2001 16:21:35 +0100 From: Nils Holland To: R Paschal Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.5-PRERELEASE announcement ? Message-ID: <20011226162135.A2481@tisys.org> Mail-Followup-To: R Paschal , freebsd-stable@FreeBSD.ORG References: <20011225205928.C29819@freeway.dcfinc.com> <3.0.5.32.20011226064544.0095fa00@mail.tucson1.az.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3.0.5.32.20011226064544.0095fa00@mail.tucson1.az.home.com>; from rpsbsd@home.com on Wed, Dec 26, 2001 at 06:45:44AM +0000 X-Operating-System: FreeBSD poison.ncptiddische.net 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE X-Machine-Uptime: 4:08PM up 6:19, 1 user, load averages: 0.01, 0.05, 0.01 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 26, 2001 at 06:45:44AM +0000, R Paschal stood up and spoke: > > Can the general project release announcements be posted into the newsgroup > comp.unix.bsd.freebsd.announce? The only thing that I've seen posted there > for a long time is the new ports added/updated by Wolfram Schneider. I guess the official announcement place is the -announce mailing list, and indeed, I guess mailing lists have a few advantages over newsgroups. I guess it really shouldn't be a problem for people who want to be informated about new releases to subscribe to that mailing list. On the other hand, it surely wouldn't hurt to forward announcements to the newsgroup, although I would suggest anybody who's serious about this to subscribe to the mailing list. Greetings Nils -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 7:34:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id E0C7A37B405; Wed, 26 Dec 2001 07:34:09 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBQFY8X14007; Wed, 26 Dec 2001 16:34:08 +0100 (CET) (envelope-from wkb) Date: Wed, 26 Dec 2001 16:34:08 +0100 From: Wilko Bulte To: Dirk Froemberg Cc: "Patrick M. Hausen" , freebsd-stable@freebsd.org Subject: Re: RELENG_4_5 Message-ID: <20011226163408.B13979@freebie.xs4all.nl> References: <200112261401.fBQE1hb47452@hugo10.ka.punkt.de> <20011226151357.A13721@freebie.xs4all.nl> <20011226154748.A11930@physik.TU-Berlin.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011226154748.A11930@physik.TU-Berlin.DE>; from dirk@freebsd.org on Wed, Dec 26, 2001 at 03:47:48PM +0100 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 26, 2001 at 03:47:48PM +0100, Dirk Froemberg wrote: > Hi! > > On Wed, Dec 26, 2001 at 03:13:57PM +0100, Wilko Bulte wrote: > > On Wed, Dec 26, 2001 at 03:01:43PM +0100, Patrick M. Hausen wrote: > > > Just a minor question: at which point in the 4.5 release cycle > > > will a RELENG_4_5 tag appear? I'd be more than happy to test > > > -PRERELEASE and/or -BETA on a couple of machines, but I'd rather > > > change my cvsupfiles from RELENG_4_4 to RELENG_4_5 than RELENG_4. > > > Saves me from changing them back after -RELEASE. > > > > RELENG_4_5 == 4.5RELEASE > > Hmm, not quite: > > RELENG_4_5_0_RELEASE == 4.5-RELEASE 8-) OK... ;-) What I was trying to say that RELENG_4_5 won't be there before 4.5 is released. > Probably RELENG_4_5 will appear not before 4.5-RELEASE. But in the end > it's up to the release engineer. I think the normal sequence of events is establishing RELENG_4_5_0 and then RELENG_4_5 to contain critical (security) fixes. But I could be wrong. Studying the commit logs might give you the ultimate clue I suppose. Wilko -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 8:57: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id CE1C037B405; Wed, 26 Dec 2001 08:56:57 -0800 (PST) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011226165652.XLAN6450.rwcrmhc52.attbi.com@bmah.dyndns.org>; Wed, 26 Dec 2001 16:56:52 +0000 Received: (from bmah@localhost) by bmah.dyndns.org (8.11.6/8.11.6) id fBQGuq400898; Wed, 26 Dec 2001 08:56:52 -0800 (PST) (envelope-from bmah) Message-Id: <200112261656.fBQGuq400898@bmah.dyndns.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Wilko Bulte Cc: Dirk Froemberg , "Patrick M. Hausen" , freebsd-stable@FreeBSD.ORG Subject: Re: RELENG_4_5 In-reply-to: <20011226163408.B13979@freebie.xs4all.nl> References: <200112261401.fBQE1hb47452@hugo10.ka.punkt.de> <20011226151357.A13721@freebie.xs4all.nl> <20011226154748.A11930@physik.TU-Berlin.DE> <20011226163408.B13979@freebie.xs4all.nl> Comments: In-reply-to Wilko Bulte message dated "Wed, 26 Dec 2001 16:34:08 +0100." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Dec 2001 08:56:52 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If memory serves me right, Wilko Bulte wrote: > On Wed, Dec 26, 2001 at 03:47:48PM +0100, Dirk Froemberg wrote: > > Hi! > > > > On Wed, Dec 26, 2001 at 03:13:57PM +0100, Wilko Bulte wrote: > > > On Wed, Dec 26, 2001 at 03:01:43PM +0100, Patrick M. Hausen wrote: > > > > Just a minor question: at which point in the 4.5 release cycle > > > > will a RELENG_4_5 tag appear? I'd be more than happy to test > > > > -PRERELEASE and/or -BETA on a couple of machines, but I'd rather > > > > change my cvsupfiles from RELENG_4_4 to RELENG_4_5 than RELENG_4. > > > > Saves me from changing them back after -RELEASE. > > > > > > RELENG_4_5 == 4.5RELEASE > > > > Hmm, not quite: > > > > RELENG_4_5_0_RELEASE == 4.5-RELEASE 8-) > > OK... ;-) What I was trying to say that RELENG_4_5 won't be there > before 4.5 is released. Well, it will, but only for about two days before the release. The RELENG_4_5 branch will be used for final tweaking of a release before the release happens...it automagically turns into the bugfix branch after the release date. The original poster referred to a "RELENG_4_5 tag". Just to clarify, RELENG_4_5 is not a tag, but it's a CVS branch. We want to create this branch fairly late in the release cycle, so that the release branch gets all of the bug fixes, MFCs, etc. applied during the release testing process. If (for example) a last-minute security fix shows up after RELENG_4_5 is created, the fix needs to get committed to HEAD, RELENG_4, and RELENG_4_5 (at the least!). > > Probably RELENG_4_5 will appear not before 4.5-RELEASE. But in the end > > it's up to the release engineer. > > I think the normal sequence of events is establishing RELENG_4_5_0 > and then RELENG_4_5 to contain critical (security) fixes. But I could > be wrong. Studying the commit logs might give you the ultimate clue I > suppose. This is indeed up to the release engineers, but there *is* a reasonably well-documented process for all of this...for the current dates for 4.5-RELEASE, see: http://www.freebsd.org/internal/releng45.html Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 8:57:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ool-18bacefa.dyn.optonline.net (ool-18bacefa.dyn.optonline.net [24.186.206.250]) by hub.freebsd.org (Postfix) with ESMTP id DFE7437B405 for ; Wed, 26 Dec 2001 08:57:47 -0800 (PST) Received: from ool-18bacefa.dyn.optonline.net (localhost [127.0.0.1]) by ool-18bacefa.dyn.optonline.net (8.11.6/8.11.6) with ESMTP id fBQGwWs04730; Wed, 26 Dec 2001 11:58:33 -0500 (EST) (envelope-from c.rued@xsb.com) Date: Wed, 26 Dec 2001 11:58:32 -0500 From: Christopher Rued To: freebsd-stable@freebsd.org Cc: c.rued@xsb.com Subject: 4_stable hangs after probing OPTi 931 Message-ID: <20011226115832.A4670@ool-18bacefa> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Balsa 1.3.0 Lines: 33 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just installed 4.4 release, and then upgraded to 4-stable earlier this week. Today, I noticed that my sound card is supported. It is a OPTi 931 ISA (PnP) sound card. Following the instructions on the the handbook page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-device.html which specifically mention this card, I added the following line to my kernel config: device pcm I did this and recompiled my kernel. After I recompile, it goes through most of the normal boot-up stuff until it probes the sound card. I see that it has probed the card, and has identified it as an OPTi931, which seems to be correct. I left it alone for about 20 minutes, and still it went no farther than printing this message out. I noticed (by searching through google) that at least one other person has had this problem. I was able to boot my machine using the same kernel after removing the sound card. Any ideas? Please copy me on any reply, as I am not on the list. - Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 9:14:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 7DB9E37B405 for ; Wed, 26 Dec 2001 09:14:39 -0800 (PST) Received: from [195.173.248.152] (helo=chain.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.33 #1) id 16JHdW-0001cv-00 for stable@freebsd.org; Wed, 26 Dec 2001 17:14:38 +0000 Received: from localhost (sven@localhost) by chain.demon.nl (8.11.6/8.11.6) with ESMTP id fBQHEXt02766 for ; Wed, 26 Dec 2001 18:14:33 +0100 (CET) (envelope-from sven@chain.demon.nl) Date: Wed, 26 Dec 2001 18:14:33 +0100 (CET) From: Sven Hazejager X-X-Sender: sven@proxy.chain.loc To: stable@freebsd.org Subject: FreeBSD on this Alpha board? Message-ID: <20011226180952.W2741-100000@proxy.chain.loc> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'm in the position to buy a used Alpha motherboard with 256MB RAM and a 533 MHz CPU. It has 2MB cache, 2 ISA slots, 2 64-bit PCI slots and 2 32-bit PCI slots, so I *think* this is a PC164LX board. The seller says the BIOS is version 5.60-3. Now the question is: will 4.4-STABLE work on this board? Does it boot from large, modern IDE disks (ie. a 40 GB one)? Thanks, Sven If I can have honesty, it's easier to overlook mistakes. -- Kirk, "Space Seed", stardate 3141.9 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 9:26:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id D61BE37B405; Wed, 26 Dec 2001 09:26:42 -0800 (PST) Received: from mail2.uniserve.com ([204.244.156.10]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 16JHp6-000OE0-00; Wed, 26 Dec 2001 09:26:36 -0800 Date: Wed, 26 Dec 2001 09:26:36 -0800 (PST) From: Tom X-Sender: tom@athena.uniserve.ca To: Keith J Cc: Peter Ong , Robert Watson , Nevermind , Murray Stokely , stable@FreeBSD.ORG, freebsd-qa@FreeBSD.ORG, bmah@FreeBSD.ORG Subject: Re: 4.5 PRERELEASE - Call for testing In-Reply-To: <001301c18de9$c7ed5240$3602a8c0@columbus.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 26 Dec 2001, Keith J wrote: > Well gee Tom.... if one end doesn't respond to negotiation... are you saying > the smart end will force a speed or duplex that can't possibly work? Lets > say I have an old 10Mbs ONLY card... are you declaring that it gets toasted > by auto-negotiate every single time? ... If the 10Mbps card is set to manual full-duplex, and the switch is set to auto-negotiate, the switch will set itself to half, creating a duplex mismatch problem (and about 1 to 7% packet loss). Both ends must be set to auto-negotiate, or both ends must be set to manual. That is the way it works. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 9:33:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 3A46537B423; Wed, 26 Dec 2001 09:33:20 -0800 (PST) Received: from mail2.uniserve.com ([204.244.156.10]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 16JHvY-000Olu-00; Wed, 26 Dec 2001 09:33:16 -0800 Date: Wed, 26 Dec 2001 09:33:16 -0800 (PST) From: Tom X-Sender: tom@athena.uniserve.ca To: Robert L Sowders Cc: Keith J , bmah@FreeBSD.ORG, freebsd-qa@FreeBSD.ORG, Murray Stokely , Nevermind , owner-freebsd-stable@FreeBSD.ORG, Peter Ong , Robert Watson , stable@FreeBSD.ORG Subject: Re: 4.5 PRERELEASE - Call for testing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 26 Dec 2001, Robert L Sowders wrote: > auto is not reliable ( at least for the fxp driver ). It always succeeds > when I force full duplex though. I've never been able to get the auto on the fxp driver to fail. In fact, in the early days of the fxp driver, autonegotiate was the only way to get the driver to do 100/full as the the media type options weren't part of ifconfig yet. However, it is important for both ends to be set for auto-negotiate. If you specify a manual setting on one end, you've disabled auto-negotiate, and it will not work. I've tested auto-negotiate on the fxp driver with the following switches: Cisco Catalyst 3524XL Cisco Catalyst 2924XL Cisco Catalyst 550x Cisco Catalyst 600x Riverstone RS-8x00 Riverstone RS-3000 Netgear FS-308 Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 9:37:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by hub.freebsd.org (Postfix) with ESMTP id 2ED9237B405 for ; Wed, 26 Dec 2001 09:37:28 -0800 (PST) Received: from eskimo.com (ripper@eskimo.com [204.122.16.13]) by mx1.eskimo.com (8.9.1a/8.8.8) with ESMTP id JAA18726; Wed, 26 Dec 2001 09:37:26 -0800 Received: (from ripper@localhost) by eskimo.com (8.9.1a/8.9.1) id JAA21301; Wed, 26 Dec 2001 09:37:26 -0800 (PST) Date: Wed, 26 Dec 2001 09:37:26 -0800 (PST) Message-Id: <200112261737.JAA21301@eskimo.com> From: Ross Lippert To: gadde@cs.duke.edu Cc: freebsd-stable@freebsd.org Subject: that atapi cdrom problem Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I was looking through the trace you have which was placed in kern-pr/31460. I cannot say for sure that I have found the bug, but I am sure I have found a terrible wrongness, I'm sure. You correctly noted that your bytecount was way way wacky. Another similar pr on this subject has a similarly corrupted bytecount in his stacktrace (pr kern/31530). bytecount looks like a negative int. Some checking reveals that bytecount should be unsigned. Personally, I like using unsigned, it gives me all 32 bits and sometimes I need them, but every once in a while it bites me in the ass because I forget that loops of the form (ui = unsigned) while(ui > 0){ui-=something;} are not going to do what you want unless something is exactly 1 or ui. I'm not sure, but I wonder if there is a gcc warning for when someone uses (ui > 0) when (ui != 0) is the equivalent. If you look in atapi_read:/sys/dev/ata/atapi-all.c you will see such a bogosity. I believe that this error results in one being able to handle read requests which are 0x800 bytes or fewer and heaven help you otherwise. There are also two bogosities of that sort in ata-disk. Just grep and see. I am cc-ing freebsd-stable so that someone can explain to me how these subtractions are justified, for I am no expert on kernel internals -- I'm just an expert on my own unsigned bugs and this looks like one. -r To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 9:42: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 03D3F37B417 for ; Wed, 26 Dec 2001 09:42:03 -0800 (PST) Received: from mail2.uniserve.com ([204.244.156.10]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 16JI3w-000Pcf-00; Wed, 26 Dec 2001 09:41:56 -0800 Date: Wed, 26 Dec 2001 09:41:56 -0800 (PST) From: Tom X-Sender: tom@athena.uniserve.ca To: Wilko Bulte Cc: sthaug@nethelp.no, kjohnso8@columbus.rr.com, stable@FreeBSD.ORG Subject: Re: 4.5 PRERELEASE - Call for testing In-Reply-To: <20011226130814.A13115@freebie.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 26 Dec 2001, Wilko Bulte wrote: ... > > Thus the advice to either use auto-negotiate everywhere, or use manual > > everywhere. One end auto-negotiate and one end manual is a recipe for > > disaster. > > So, that implies that in these cases non-managable switches are doomed > as you cannot 'hard-set' them to some value. Not necessarily. I have an unmanaged Netgear FS308 switch (typical cheap etherswitch), but it supports autonegotiate. When I plug in a FreeBSD box with a fxp card, the lights on the front of the switch show that it has properly negotiated 100/full. The fact is, most ethernet hardware that says it support auto-negotiate, actually does, and it actually works. Auto-negotiation has gotten a reputation for being unreliable because users end up disabling auto on one end and still expect it to work. Auto-negotiation != auto-detection. > -- > | / o / /_ _ email: wilko@FreeBSD.org > |/|/ / / /( (_) Bulte Arnhem, The Netherlands > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 9:46:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rfnj.org (rfnj.org [216.239.237.194]) by hub.freebsd.org (Postfix) with ESMTP id C582737B405 for ; Wed, 26 Dec 2001 09:46:15 -0800 (PST) Received: from megalomaniac.biosys.net (megalomaniac.rfnj.org [216.239.237.200]) by rfnj.org (Postfix) with ESMTP id 2EDFA137DB; Wed, 26 Dec 2001 12:47:05 -0500 (EST) Message-Id: <5.1.0.14.0.20011226123443.00aafe40@rfnj.org> X-Sender: asym@rfnj.org X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 26 Dec 2001 12:45:08 -0500 To: Tom From: Allen Landsidel Subject: Re: 4.5 PRERELEASE - Call for testing Cc: freebsd-stable@freebsd.org In-Reply-To: References: <001301c18de9$c7ed5240$3602a8c0@columbus.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 09:26 AM 12/26/2001 -0800, you wrote: >On Wed, 26 Dec 2001, Keith J wrote: > > > Well gee Tom.... if one end doesn't respond to negotiation... are you > saying > > the smart end will force a speed or duplex that can't possibly work? Lets > > say I have an old 10Mbs ONLY card... are you declaring that it gets toasted > > by auto-negotiate every single time? >... > > If the 10Mbps card is set to manual full-duplex, and the switch is set >to auto-negotiate, the switch will set itself to half, creating a duplex >mismatch problem (and about 1 to 7% packet loss). Both ends must be set >to auto-negotiate, or both ends must be set to manual. That is the way it >works. This is a pretty silly, uninformed response. First, just off the top, it doesn't make any sense. What if you have a "dumb" auto-negotiating switch? I have such a switch, a Linksys EtherFast II 16port 10/100. There is no way to tell the switch what setting any of the ports should be in, nor have I ever needed such an option. The switch has never failed to negotiate the correct setting with whatever is plugged into it, nor has it ever had a problem matching whatever I assign to an interface I have plugged into it. This is evidenced by the fact that the switch has two LEDs per port. The first one is either green for 100Mbit or orange for 10Mbit, the second is on if the port is full-duplex, off if it's half-duplex. I think perhaps you should stop repeating yourself and go read up on how autonegotiation actually works.. what you've been saying is only true (in my experience) if you're plugging one NIC directly into another via a crossover cable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 9:55: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 8C9D737B419 for ; Wed, 26 Dec 2001 09:54:55 -0800 (PST) Received: (qmail 2355 invoked by uid 1001); 26 Dec 2001 17:54:53 +0000 (GMT) To: all@biosys.net Cc: freebsd-stable@freebsd.org Subject: Re: 4.5 PRERELEASE - Call for testing From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 26 Dec 2001 12:45:08 -0500" References: <5.1.0.14.0.20011226123443.00aafe40@rfnj.org> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 26 Dec 2001 18:54:53 +0100 Message-ID: <2353.1009389293@verdi.nethelp.no> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > This is a pretty silly, uninformed response. First, just off the top, it > doesn't make any sense. What if you have a "dumb" auto-negotiating > switch? I have such a switch, a Linksys EtherFast II 16port 10/100. There > is no way to tell the switch what setting any of the ports should be in, > nor have I ever needed such an option. As long as auto-negotiation works (and any cards plugged into this switch are set to auto-negotiate), you should be fine. > The switch has never failed to negotiate the correct setting with whatever > is plugged into it, nor has it ever had a problem matching whatever I > assign to an interface I have plugged into it. If whatever you plug into the switch is set *not* to autonegotiate (ie. is set manually to full duplex), you cannot count on the switch to get the duplex setting correct. In some cases it'll work, in other cases it won't. If it always works for you - great. But don't count on this working as a general rule - there are plenty of examples to disprove it. > I think perhaps you should stop repeating yourself and go read up on how > autonegotiation actually works.. what you've been saying is only true (in > my experience) if you're plugging one NIC directly into another via a > crossover cable. He's certainly not the only one who firmly believes that one end set to auto-negotiate and one end set manually is a good way to create problems for yourself. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 9:56:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from haloflightleader.net (adsl-63-197-56-193.dsl.lsan03.pacbell.net [63.197.56.193]) by hub.freebsd.org (Postfix) with ESMTP id B9AB037B417; Wed, 26 Dec 2001 09:56:23 -0800 (PST) Received: from ongppla (hogan-and-hartson-llp.Washington.cw.net [208.173.12.150]) by haloflightleader.net (8.11.6/8.11.6) with SMTP id fBQHuE906113; Wed, 26 Dec 2001 09:56:14 -0800 (PST) (envelope-from peter@haloflightleader.net) Message-ID: <007201c18e36$45a05c40$245b1486@hhlaw.com> From: "Peter/Los Angeles, CA" To: "Tom" , "Keith J" Cc: "Robert Watson" , "Nevermind" , "Murray Stokely" , , , References: Subject: Re: 4.5 PRERELEASE - Call for testing Date: Wed, 26 Dec 2001 09:53:39 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've actually solved the problem. It was due to the client being full, and no space to write cache/swap. But I've since fixed that, and there was no problem on the backend to begin with. Peter ----- Original Message ----- From: "Tom" To: "Keith J" Cc: "Peter Ong" ; "Robert Watson" ; "Nevermind" ; "Murray Stokely" ; ; ; Sent: Tuesday, December 25, 2001 10:50 AM Subject: Re: 4.5 PRERELEASE - Call for testing > > On Tue, 25 Dec 2001, Keith J wrote: > > ... > > Another possibility is you do not have a Samba problem, but a network > > problem with auto-negotiate. Some older 10/100 cards and switch combinations > > step all over each other. You should lock down one end to a specific speed > ... > > That is bad advice. Auto-negotiation is not auto-detect. If you > disable auto-negotiate at one end and specify manual settings, you must > disable it on the other end too, and specify the SAME manual settings. > Either use auto-negotiate everywhere, or use manual everywhere. I would > recommend using auto everywhere. > > Tom > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 10: 2:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rfnj.org (rfnj.org [216.239.237.194]) by hub.freebsd.org (Postfix) with ESMTP id 52F6D37B416 for ; Wed, 26 Dec 2001 10:02:34 -0800 (PST) Received: from megalomaniac.biosys.net (megalomaniac.rfnj.org [216.239.237.200]) by rfnj.org (Postfix) with ESMTP id 6371C137DB; Wed, 26 Dec 2001 13:03:33 -0500 (EST) Message-Id: <5.1.0.14.0.20011226125628.00b08e10@rfnj.org> X-Sender: asym@rfnj.org X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 26 Dec 2001 13:02:11 -0500 To: sthaug@nethelp.no From: Allen Landsidel Subject: Re: 4.5 PRERELEASE - Call for testing Cc: freebsd-stable@freebsd.org In-Reply-To: <2353.1009389293@verdi.nethelp.no> References: <5.1.0.14.0.20011226123443.00aafe40@rfnj.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 06:54 PM 12/26/2001 +0100, you wrote: > > This is a pretty silly, uninformed response. First, just off the top, it > > doesn't make any sense. What if you have a "dumb" auto-negotiating > > switch? I have such a switch, a Linksys EtherFast II 16port > 10/100. There > > is no way to tell the switch what setting any of the ports should be in, > > nor have I ever needed such an option. > >As long as auto-negotiation works (and any cards plugged into this switch >are set to auto-negotiate), you should be fine. Autonegotiation should always work. It's a standard. Autosensing isn't, and that's why it's been replaced/superceeded. > > The switch has never failed to negotiate the correct setting with whatever > > is plugged into it, nor has it ever had a problem matching whatever I > > assign to an interface I have plugged into it. > >If whatever you plug into the switch is set *not* to autonegotiate (ie. >is set manually to full duplex), you cannot count on the switch to get >the duplex setting correct. In some cases it'll work, in other cases >it won't. If it always works for you - great. But don't count on this >working as a general rule - there are plenty of examples to disprove it. You're confusing two things, auto-negotiation and auto-sensing, as is Tom. Auto-negotiation is *always* on, even if you force a certain speed/duplex. This is what tells the switch/hub/whatever it's settings. Auto-sensing is the old method if determining the line speed only, not the duplex, and was full of all kinds of problems. As a general rule, if you have an auto *negotiating* switch/hub and an auto *negotiating* NIC, then this will always work. If one or or the other is auto *sensing* then problems may occur, but this is why the two terms exist, and why auto-sensing hasn't been available for quite some time. Tom's reply stated that if you turned auto-negotiation off by forcing a speed/duplex setting on either end that it would cause problems. This simply isn't true because you can't turn auto-negotating off, and forcing a speed/duplex setting doesn't do this.. what it does do is forces the other end to negotiate this setting, if it is available. The negotiation still occurs. > > I think perhaps you should stop repeating yourself and go read up on how > > autonegotiation actually works.. what you've been saying is only true (in > > my experience) if you're plugging one NIC directly into another via a > > crossover cable. > >He's certainly not the only one who firmly believes that one end set to >auto-negotiate and one end set manually is a good way to create problems >for yourself. See above. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 10:41:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sv07e.atm-tzs.kmjeuro.com (sv07e.atm-tzs.kmjeuro.com [193.81.94.207]) by hub.freebsd.org (Postfix) with ESMTP id 906E637B405 for ; Wed, 26 Dec 2001 10:41:24 -0800 (PST) Received: (from root@localhost) by sv07e.atm-tzs.kmjeuro.com (8.11.5/8.11.4) id fBQIfM189384 for freebsd-stable@freebsd.org; Wed, 26 Dec 2001 19:41:22 +0100 (CET) (envelope-from k.joch@kmjeuro.com) Received: from karl (9caf2bb306fead67e8a2bbf008dc43d9@adsl.ooe.kmjeuro.com [193.154.186.21]) (authenticated) by sv07e.atm-tzs.kmjeuro.com (8.11.5/8.11.4) with ESMTP id fBQIf3a88985; Wed, 26 Dec 2001 19:41:03 +0100 (CET) (envelope-from k.joch@kmjeuro.com) Message-ID: <01ad01c18e3d$00a18860$0a05a8c0@ooe.kmjeuro.com> From: "Karl M. Joch" To: "Gerhard Sittig" , References: <05ae01c18d80$df7bfe20$0a05a8c0@ooe.kmjeuro.com> <20011226144617.P1494@shell.gsinet.sittig.org> Subject: Re: 4.5 PRERELEASE - Call for testing (Kapok Notebook) Date: Wed, 26 Dec 2001 19:41:51 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X--virus-scanner: scanned for Virus and dangerous attachments on sv07e.atm-tzs.kmjeuro.com (System Setup/Maintainance: http://www.ctseuro.com/) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sorry for not adding the original post. anyway, i tried building 4.5pre on a testbox and made a custom kernel (as in the original post. this one worked up to 4.1 or 4.2. not 100% sure). createt loader.conf with your suggestions. the result is still the same as with 4.4 in the original post. i add the original post at the ed of this message. pci_cfgintr_linked: linked (60) to hard routed irq 10 fatal trap 12: page fault while in kernel mode fault virtual address = 0xeb65d instruction pointer = 0x8:0xc00eb55e stack pointer = 0x10:0xc0693d6c frame pointer= 0x10:0xc0693d6c code segment = base 0x0, limit 0xfffff, type 0x1b DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam trap number = 12 panic: page fault -- -- Best regards / Mit freundlichen Gruessen, Karl M. Joch ----- Original Message ----- From: "Gerhard Sittig" To: Sent: Wednesday, December 26, 2001 2:46 PM Subject: Re: 4.5 PRERELEASE - Call for testing > On Tue, Dec 25, 2001 at 21:15 +0100, Karl M. Joch wrote: > > > > i would like to get my notebook,which hangs on boot (pcic), to run again > > with freebsd. was there any recent changes or any hints how i could get > > around that problem? (the problem was posted with KAPOK in the subject). > > You didn't state (again) where it "hangs on boot". Plus I didn't > feel like crawling the archives again (BTW Message-Id's are far > better handles than single words in the subject line). Is your > problem by any chance the famous(?) > hw.pcic.intr_path=1 > hw.pcic.irq=0 > thingy? If these settings help you at boot time, just put them > into your /boot/loader.conf and things should keep working. These > settings are not in UPDATING as I can see, but Warner Losh posted > quite a few of these instructions again and again into the lists > (both -stable and -mobile). And these lines might be in the 4.4 > RELNOTES, too (don't have them handy ATM). > > For your searching here's the initial announcement, while many > people asked this question again and got answered, too. :) > Message-Id: <200108260507.f7Q570W08734@harmony.village.org> > From: Warner Losh > To: mobile@freebsd.org > Cc: doc@freebsd.org > Date: Sat, 25 Aug 2001 23:06:59 -0600 > Subject: MFC: ISA routing support > > > virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 > Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > ### original #### if i boot with a kernel without pcic support i get the following dmesg.boot. i also included the config for the kernel which panics. i have done a cvsup of the latest source tree before building the kernel (21/10/01). it panics with: pcic0: chip is in D3 power mode -- setting to D0 oci_cfgintr_linked: linked (60) to hard routed irq 10 Fatal trap 12: page fault while in kernel mode instruction pointer: 0x8:0xc00eb55e Karl Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-STABLE #0: Sat Oct 20 11:51:48 CEST 2001 root@adsl.ooe.kmjeuro.com:/usr/obj/usr/src.4.0/sys/WSNB Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (233.86-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 134217728 (131072K bytes) avail memory = 126570496 (123604K bytes) Preloaded elf kernel "kernel" at 0xc03a6000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk Using $PIR table, 4 entries at 0xc00fe840 apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x1100-0x110f at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 1.2 irq 0 chip1: port 0x1400-0x140f at device 1.3 on pci0 pci0: at 2.0 ##### kernel panics here when running with pcic ############################################ chip2: at device 10.0 on pci0 chip3: at device 10.1 on pci0 orm0:
This should be moved to chat, hardware, hackers, you pick it.

Regardless of what the standard says, it has been my experience that if you have a connection that fails to autoneg to full duplex, then forcing the freebsd nic to 100 full will result in the expected behavior of a 100 full connection.  During the negotiation phase the nic says I can only do 100 full and the switch responds with 100 full.

Recent experience with HP-Procurve and NBase Mega switches confirmed that they continually refused to autoneg 100 full until the nics were forced to 100 full.  Subsequently turning the nics back to autoneg produced 100 full connections.  Why this occurred is beyond me, but after three days of testing that was the fix.

It may be that this is not the experience of the other readers of this thread.  That's fine, all I'm saying is, if you're having trouble with full duplex then try forcing the nic to full and see what happens, it works for me.

This really should be moved off stable now.



Ulf Zimmermann <ulf@Alameda.net>
Sent by: owner-freebsd-stable@FreeBSD.ORG

12/26/2001 02:29 PM
Please respond to ulf

       
        To:        "Peter/Los Angeles, CA" <peter@haloflightleader.net>
        cc:        Sam Drinkard <sam@wa4phy.net>, Allen Landsidel <all@biosys.net>, sthaug@nethelp.no, freebsd-stable@FreeBSD.ORG
        Subject:        Re: 4.5 PRERELEASE - Call for testing


On Wed, Dec 26, 2001 at 02:22:15PM -0800, Peter/Los Angeles, CA wrote:
> Please correct me if I'm wrong, but isn't it kind of strange that
> auto-sensing/auto-negotiating must be enabled on both sides for the feature
> to work a bit strange?
>
> At home, I have a Netgear FS116, a 16-Port unmanaged switch.  It is
> auto-sensing/full-duplex 10/100Mbits/sec switch.  Therefore, we cannot
> control how it will behave.
>
> On the other hand, I have network cards on my computer which I can set to
> full/half/auto/10/100, whatever combination I like, and yet, the switch will
> continue to work.
>
> What I'm getting at is that just because one end is not set to
> auto-negotiate/auto-sense that there will be no communication at all.  Say,
> that one end is set manually, and the other end is automatic.  The automatic
> end will set itself to the parameters of the one that is manually set.  This
> is how my network works.  Thus, I don't believe that both ends, need to be
> set the same way in order to work in this scenario.
>
> The automatic will automatically negotiate/auto-sense to whatever can't be
> changed, as a result, they work.  Or is this even what you folks are arguing
> about?

I do not know if this is written in the standard, but I have seen devices
where if you turn off AutoNeg, they won't respond at all to the packets.
But I have also seens devices which will still respond, but just to their
fixed setting. I personal prefer it that if I turn off autoneg, it won't
do anything, because that gives you a fixed point. Any production system
I always set switch and host to full 100.

--
Regards, Ulf.

---------------------------------------------------------------------
Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204
You can find my resume at: http://seven.Alameda.net/~ulf/resume.html

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message

--=_alternative 0082731E88256B2E_=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 15:55:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 23E9B37B416; Wed, 26 Dec 2001 15:55:44 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBQNtfK48250; Wed, 26 Dec 2001 15:55:41 -0800 (PST) (envelope-from dillon) Date: Wed, 26 Dec 2001 15:55:41 -0800 (PST) From: Matthew Dillon Message-Id: <200112262355.fBQNtfK48250@apollo.backplane.com> To: Søren Schmidt Cc: Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers References: <200112262315.fBQNFue42555@freebsd.dk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :It seems Matthew Gilbert wrote: :> > So, general question to everyone having crashes during heavy :> > IDE workloads: Please post your /var/run/dmesg.boot :> > output. : :> atapci0: port 0xd000-0xd00f at device 7.1 on : :You have the VIA 82c686b southbridge chip which is known to cause severe :data corruption problems if the BIOS does not setup the northbidge :chip correctly. Please check with your board vendor if they have a :new updated BIOS that fixes this problem. This is not an ATA specific :problem, but a problem with the PCI subsystem in general on these :chips that manifests it self on high PCI load (which the ATA subsytem :is quite capable of delivering)... : :A fix for this is present in -current, and if I get permission from :the RE, it will go into 4.5 also, but a BIOS fix is by far the right :way to fix this problem. : :-Søren Soren, if you post a patch for 4.x I will be happy to follow-up with Brady. I've been working with Brady for several days now trying to track down corruption in the vm_page array. I *really* want to know if a VIA chipset patch solves his problem, because it would also explain about a dozen similar bug reports over the last 6 months. (Which would also be good backing to get it into 4.5). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16: 1:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 076D737B405; Wed, 26 Dec 2001 16:01:24 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBR01Ns48341; Wed, 26 Dec 2001 16:01:23 -0800 (PST) (envelope-from dillon) Date: Wed, 26 Dec 2001 16:01:23 -0800 (PST) From: Matthew Dillon Message-Id: <200112270001.fBR01Ns48341@apollo.backplane.com> To: Søren Schmidt , Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers References: <200112262315.fBQNFue42555@freebsd.dk> <200112262355.fBQNtfK48250@apollo.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :: ::> atapci0: port 0xd000-0xd00f at device 7.1 on :: ::You have the VIA 82c686b southbridge chip which is known to cause severe ::data corruption problems if the BIOS does not setup the northbidge ::chip correctly. Please check with your board vendor if they have a ::new updated BIOS that fixes this problem. This is not an ATA specific ::problem, but a problem with the PCI subsystem in general on these ::chips that manifests it self on high PCI load (which the ATA subsytem ::is quite capable of delivering)... :: ::A fix for this is present in -current, and if I get permission from ::the RE, it will go into 4.5 also, but a BIOS fix is by far the right ::way to fix this problem. :: ::-Søren : : Soren, if you post a patch for 4.x I will be happy to follow-up : with Brady. I've been working with Brady for several days now trying : to track down corruption in the vm_page array. I *really* want to know : if a VIA chipset patch solves his problem, because it would : also explain about a dozen similar bug reports over the last 6 months. : (Which would also be good backing to get it into 4.5). Sorry, I meant I'd follow up with Matthew Gilbert. Also, I've been trying to track down a crash in nfs_node that Nils Holland has been having - he appears to have the same chipset and could have the same problem, and he can reproduce the panic very consistently within a few hours. Brady has an older chipset. Are there any known problems with this chipset? pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe400-0xe40f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16:17:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from oddjob.trewitt.org (adsl-216-102-95-11.dsl.snfc21.pacbell.net [216.102.95.11]) by hub.freebsd.org (Postfix) with ESMTP id C04C237B416 for ; Wed, 26 Dec 2001 16:17:17 -0800 (PST) Received: from trewitt.org (g4.trewitt.org [10.0.0.4]) by oddjob.trewitt.org (8.11.3/8.11.1) with ESMTP id fBR0HHJ05142 for ; Wed, 26 Dec 2001 16:17:17 -0800 (PST) (envelope-from glenn@trewitt.org) Message-ID: <3C2A688C.AFAC2233@trewitt.org> Date: Wed, 26 Dec 2001 16:17:18 -0800 From: Glenn Trewitt Reply-To: glenn@trewitt.org X-Mailer: Mozilla 4.78 (Macintosh; U; PPC) X-Accept-Language: en,pdf MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: RELENG_4_5 References: <200112261401.fBQE1hb47452@hugo10.ka.punkt.de> Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I think that the original question, which I also need answered, is "What CVS tag should I use if I want to test 4.5-PRELEASE?" I need a clue! - Glenn Trewitt "Patrick M. Hausen" wrote: > Hello all! > > Just a minor question: at which point in the 4.5 release cycle > will a RELENG_4_5 tag appear? I'd be more than happy to test > -PRERELEASE and/or -BETA on a couple of machines, but I'd rather > change my cvsupfiles from RELENG_4_4 to RELENG_4_5 than RELENG_4. > Saves me from changing them back after -RELEASE. > > Wouldn't it make sense if -BETAs and -RCs were already tagged > RELENG_4_X? > > Regards, > Patrick M. Hausen > Technical Director To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16:20:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vortex.wa4phy.net (cc449817-a.mrtnz1.ga.home.com [24.12.79.51]) by hub.freebsd.org (Postfix) with ESMTP id 6843337B416 for ; Wed, 26 Dec 2001 16:20:51 -0800 (PST) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.11.6/8.11.6) with ESMTP id fBR0Ko117214 for ; Wed, 26 Dec 2001 19:20:50 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3C2A6962.16CDFAB2@vortex.wa4phy.net> Date: Wed, 26 Dec 2001 19:20:50 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-PRERELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: 82C686 chipset Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mail to Soren bounces, so will try this approach... Have there been any issues with the 82C686 ATA66 chipsets w/r/t corruption? Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16:22:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 49FDF37B416 for ; Wed, 26 Dec 2001 16:22:19 -0800 (PST) Received: from mail2.uniserve.com ([204.244.156.10]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 16JOJG-000C6G-00; Wed, 26 Dec 2001 16:22:11 -0800 Date: Wed, 26 Dec 2001 16:22:10 -0800 (PST) From: Tom X-Sender: tom@athena.uniserve.ca To: "Peter/Los Angeles, CA" Cc: Sam Drinkard , Allen Landsidel , sthaug@nethelp.no, freebsd-stable@FreeBSD.ORG Subject: Re: 4.5 PRERELEASE - Call for testing In-Reply-To: <011601c18e5b$cb3b16e0$245b1486@hhlaw.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 26 Dec 2001, Peter/Los Angeles, CA wrote: > Please correct me if I'm wrong, but isn't it kind of strange that > auto-sensing/auto-negotiating must be enabled on both sides for the feature > to work a bit strange? It isn't strange at all. During auto-negotation both ends exchange a list of capabilities that they support, and they decide what capabilities to enable. If you disable auto-negotiate at one end, the end still doing auto-negotiating will default to half-duplex. The speed is only thing that can automaticatically detected. ... > On the other hand, I have network cards on my computer which I can set to > full/half/auto/10/100, whatever combination I like, and yet, the switch will > continue to work. Not the duplex settings. If you disable auto-negotiating on your NIC, by forcing it to full-duplex, your auto-negotiating switch won't know what you support and default to half-duplex. If the duplex is mistmatched, everything seems to work, but there will be a 1 to 7% packet loss. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16:22:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail2.sdc1.sfba.home.com (femail2.sdc1.sfba.home.com [24.0.95.82]) by hub.freebsd.org (Postfix) with ESMTP id 3CADD37B43A for ; Wed, 26 Dec 2001 16:22:26 -0800 (PST) Received: from crazyhorse ([24.21.114.209]) by femail2.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20011227002225.SWR11081.femail2.sdc1.sfba.home.com@crazyhorse>; Wed, 26 Dec 2001 16:22:25 -0800 Message-Id: <3.0.5.32.20011226172225.00959530@mail.tucson1.az.home.com> X-Sender: rpsbsd@mail.tucson1.az.home.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 26 Dec 2001 17:22:25 To: Nils Holland From: R Paschal Subject: Re: 4.5-PRERELEASE announcement ? Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <20011226162135.A2481@tisys.org> References: <3.0.5.32.20011226064544.0095fa00@mail.tucson1.az.home.com> <20011225205928.C29819@freeway.dcfinc.com> <3.0.5.32.20011226064544.0095fa00@mail.tucson1.az.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 04:21 PM 12/26/01 +0100, Nils Holland wrote: >On Wed, Dec 26, 2001 at 06:45:44AM +0000, R Paschal stood up and spoke: >> >> Can the general project release announcements be posted into the newsgroup >> comp.unix.bsd.freebsd.announce? The only thing that I've seen posted there >> for a long time is the new ports added/updated by Wolfram Schneider. > >I guess the official announcement place is the -announce mailing list, and >indeed, I guess mailing lists have a few advantages over newsgroups. I >guess it really shouldn't be a problem for people who want to be informated >about new releases to subscribe to that mailing list. On the other hand, >it surely wouldn't hurt to forward announcements to the newsgroup, >although I would suggest anybody who's serious about this to subscribe to >the mailing list. From personal experience, I see one major problem with that. There are a lot of people using ISPs with, for what-ever reason, misconfigured mail servers. There's not anything they can do about it, either. I know, because I was in that position from Dec. 11, 2000, to mid Aug. 19, 2001. The ISP I used, ultrasw.com, mapped all their clients mail to one IP address. When a reverse DNS lookup was done on the IP address, the name returned was the alphabetically first in the list. But not anymore! They now support no reverse lookups. You can try it yourself if you don't believe it. Do a whois or nslookup on ultrasw.com and then do a reverse DNS lookup on their DNS server, ns1.ultrasw.com, 204.17.51.1. Then look up their mail server, mail.ultrasw.com and get its IP, 66.181.240.7 and do a reverse DNS lookup on it. You can ping them. You can find them at www.ultrasw.com and see what business they're in. Can anybody on that ISP subscribe, post questions, or submit PRs? I don't think so. They can, however read the newsgroups. What do you suppose they think of the mailing list anti-spam policies, especially after visiting http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html, which makes no mention of this policy, and they get a cryptic response from freebsd.org? BTW, from what I saw in questions the last few months, that policy doesn't do much to stop spam. It also says a lot that the only freebsd mail policy that's enforced with an iron fist is the unwritten one. Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16:23: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from web10104.mail.yahoo.com (web10104.mail.yahoo.com [216.136.130.54]) by hub.freebsd.org (Postfix) with SMTP id 629F737B44B for ; Wed, 26 Dec 2001 16:22:49 -0800 (PST) Message-ID: <20011227002248.40200.qmail@web10104.mail.yahoo.com> Received: from [65.88.96.239] by web10104.mail.yahoo.com via HTTP; Wed, 26 Dec 2001 16:22:48 PST Date: Wed, 26 Dec 2001 16:22:48 -0800 (PST) From: John Hanley Subject: Re: 4.5 PRERELEASE - Call for testing To: Keith J Cc: Tom , stable@FreeBSD.ORG, freebsd-qa@FreeBSD.ORG In-Reply-To: <001301c18de9$c7ed5240$3602a8c0@columbus.rr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- Keith J wrote: > Well gee Tom.... if one end doesn't respond to negotiation... are you > saying the smart end will force a speed or duplex that can't possibly > work? Lets say I have an old 10Mbs ONLY card... are you declaring > that it gets toasted by auto-negotiate every single time? OK, this is boring. Debating opinions is occasionally useful, but facts are facts and flamage won't change them. Please let Cisco have the last word on this topic: http://www.cisco.com/warp/public/473/46.html Per the IEEE 802.3u specification, it not possible to manually configure one link partner for 100 Mbps full-duplex and still autonegotiate to full-duplex with the other link partner. Attempting to configure one link partner for 100 Mbps full-duplex and the other link partner for auto-negotiation will result in a duplex mismatch. This is a result of one link partner auto-negotiating and not seeing any auto-negotiation parameters from the other link partner and defaulting to half-duplex. __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16:25:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from seven.Alameda.net (seven.Alameda.net [64.81.63.137]) by hub.freebsd.org (Postfix) with ESMTP id D4AF437B405 for ; Wed, 26 Dec 2001 16:25:10 -0800 (PST) Received: by seven.Alameda.net (Postfix, from userid 1000) id 8A08A3A239; Wed, 26 Dec 2001 16:25:10 -0800 (PST) Date: Wed, 26 Dec 2001 16:25:10 -0800 From: Ulf Zimmermann To: Glenn Trewitt Cc: freebsd-stable@FreeBSD.ORG Subject: Re: RELENG_4_5 Message-ID: <20011226162510.L90222@seven.alameda.net> Reply-To: ulf@Alameda.net References: <200112261401.fBQE1hb47452@hugo10.ka.punkt.de> <3C2A688C.AFAC2233@trewitt.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C2A688C.AFAC2233@trewitt.org>; from glenn@trewitt.org on Wed, Dec 26, 2001 at 04:17:18PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 4.4-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 26, 2001 at 04:17:18PM -0800, Glenn Trewitt wrote: > I think that the original question, which I also need answered, is > "What CVS tag should I use if I want to test 4.5-PRELEASE?" > I need a clue! RELENG_4 > > - Glenn Trewitt > > "Patrick M. Hausen" wrote: > > > Hello all! > > > > Just a minor question: at which point in the 4.5 release cycle > > will a RELENG_4_5 tag appear? I'd be more than happy to test > > -PRERELEASE and/or -BETA on a couple of machines, but I'd rather > > change my cvsupfiles from RELENG_4_4 to RELENG_4_5 than RELENG_4. > > Saves me from changing them back after -RELEASE. > > > > Wouldn't it make sense if -BETAs and -RCs were already tagged > > RELENG_4_X? > > > > Regards, > > Patrick M. Hausen > > Technical Director > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://seven.Alameda.net/~ulf/resume.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16:28:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from haloflightleader.net (adsl-63-197-56-193.dsl.lsan03.pacbell.net [63.197.56.193]) by hub.freebsd.org (Postfix) with ESMTP id A07FF37B416; Wed, 26 Dec 2001 16:28:42 -0800 (PST) Received: from ongppla (hogan-and-hartson-llp.Washington.cw.net [208.173.12.150]) by haloflightleader.net (8.11.6/8.11.6) with SMTP id fBR0Sa906798; Wed, 26 Dec 2001 16:28:37 -0800 (PST) (envelope-from peter@haloflightleader.net) Message-ID: <01cf01c18e6d$59b81420$245b1486@hhlaw.com> From: "Peter/Los Angeles, CA" To: "John Hanley" , "Keith J" Cc: "Tom" , , References: <20011227002248.40200.qmail@web10104.mail.yahoo.com> Subject: Re: 4.5 PRERELEASE - Call for testing Date: Wed, 26 Dec 2001 16:27:56 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG No!!! We must continue the revolution!!! Welcome to the revolution!!! AAAAHHH!!! Auto-neg/Auto-sense should be the only subject in this list for the next 10 years until we resolve this issue. Continue the fight laddies!!! Arrgggh!!! Fight for your right to auto-negotiate. Peter PS Was just kidding. I started this thread, but it was just about a Samba problem that didn't even have anything to do with layer 2 devices. Anyway, like I've posted before, the problem was solved, and the culprits were on the application layer, not the data link. No animals were harmed in the creation of this email. ----- Original Message ----- From: "John Hanley" To: "Keith J" Cc: "Tom" ; ; Sent: Wednesday, December 26, 2001 4:22 PM Subject: Re: 4.5 PRERELEASE - Call for testing > --- Keith J wrote: > > Well gee Tom.... if one end doesn't respond to negotiation... are you > > saying the smart end will force a speed or duplex that can't possibly > > work? Lets say I have an old 10Mbs ONLY card... are you declaring > > that it gets toasted by auto-negotiate every single time? > > OK, this is boring. Debating opinions is occasionally useful, > but facts are facts and flamage won't change them. Please let > Cisco have the last word on this topic: > > http://www.cisco.com/warp/public/473/46.html > > Per the IEEE 802.3u specification, it not possible to manually > configure one link partner for 100 Mbps full-duplex and still > autonegotiate to full-duplex with the other link partner. > Attempting to configure one link partner for 100 Mbps full-duplex > and the other link partner for auto-negotiation will result in a > duplex mismatch. This is a result of one link partner auto-negotiating > and not seeing any auto-negotiation parameters from the other link > partner and defaulting to half-duplex. > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16:30:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from haloflightleader.net (adsl-63-197-56-193.dsl.lsan03.pacbell.net [63.197.56.193]) by hub.freebsd.org (Postfix) with ESMTP id 4EA4737B41B; Wed, 26 Dec 2001 16:30:35 -0800 (PST) Received: from ongppla (hogan-and-hartson-llp.Washington.cw.net [208.173.12.150]) by haloflightleader.net (8.11.6/8.11.6) with SMTP id fBR0UK906812; Wed, 26 Dec 2001 16:30:21 -0800 (PST) (envelope-from peter@haloflightleader.net) Message-ID: <01dd01c18e6d$9847b420$245b1486@hhlaw.com> From: "Peter/Los Angeles, CA" To: , "Robert L Sowders" Cc: "Allen Landsidel" , , , "Sam Drinkard" , References: Subject: Re: 4.5 PRERELEASE - Call for testing Date: Wed, 26 Dec 2001 16:29:40 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01D8_01C18E2A.847ADE60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_01D8_01C18E2A.847ADE60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Look, I'm not for flames myself, but I have to say it gets a whole lot = more interesting when there's a forest fire going on. It's like a Jerry = Springer show except it's really quiet. Peter ----- Original Message -----=20 From: Robert L Sowders=20 To: ulf@Alameda.net=20 Cc: Allen Landsidel ; freebsd-stable@FreeBSD.ORG ; = owner-freebsd-stable@FreeBSD.ORG ; Peter/Los Angeles, CA ; Sam Drinkard = ; sthaug@nethelp.no=20 Sent: Wednesday, December 26, 2001 3:44 PM Subject: Re: 4.5 PRERELEASE - Call for testing This should be moved to chat, hardware, hackers, you pick it.=20 Regardless of what the standard says, it has been my experience that = if you have a connection that fails to autoneg to full duplex, then = forcing the freebsd nic to 100 full will result in the expected behavior = of a 100 full connection. During the negotiation phase the nic says I = can only do 100 full and the switch responds with 100 full.=20 Recent experience with HP-Procurve and NBase Mega switches confirmed = that they continually refused to autoneg 100 full until the nics were = forced to 100 full. Subsequently turning the nics back to autoneg = produced 100 full connections. Why this occurred is beyond me, but = after three days of testing that was the fix.=20 It may be that this is not the experience of the other readers of this = thread. That's fine, all I'm saying is, if you're having trouble with = full duplex then try forcing the nic to full and see what happens, it = works for me.=20 This really should be moved off stable now.=20 Ulf Zimmermann =20 Sent by: owner-freebsd-stable@FreeBSD.ORG=20 12/26/2001 02:29 PM=20 Please respond to ulf=20 =20 To: "Peter/Los Angeles, CA" = =20 cc: Sam Drinkard , Allen = Landsidel , sthaug@nethelp.no, = freebsd-stable@FreeBSD.ORG=20 Subject: Re: 4.5 PRERELEASE - Call for testing=20 On Wed, Dec 26, 2001 at 02:22:15PM -0800, Peter/Los Angeles, CA wrote: > Please correct me if I'm wrong, but isn't it kind of strange that > auto-sensing/auto-negotiating must be enabled on both sides for the = feature > to work a bit strange? >=20 > At home, I have a Netgear FS116, a 16-Port unmanaged switch. It is > auto-sensing/full-duplex 10/100Mbits/sec switch. Therefore, we = cannot > control how it will behave. >=20 > On the other hand, I have network cards on my computer which I can = set to > full/half/auto/10/100, whatever combination I like, and yet, the = switch will > continue to work. >=20 > What I'm getting at is that just because one end is not set to > auto-negotiate/auto-sense that there will be no communication at = all. Say, > that one end is set manually, and the other end is automatic. The = automatic > end will set itself to the parameters of the one that is manually = set. This > is how my network works. Thus, I don't believe that both ends, need = to be > set the same way in order to work in this scenario. >=20 > The automatic will automatically negotiate/auto-sense to whatever = can't be > changed, as a result, they work. Or is this even what you folks are = arguing > about? I do not know if this is written in the standard, but I have seen = devices where if you turn off AutoNeg, they won't respond at all to the = packets. But I have also seens devices which will still respond, but just to = their fixed setting. I personal prefer it that if I turn off autoneg, it = won't do anything, because that gives you a fixed point. Any production = system I always set switch and host to full 100. --=20 Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://seven.Alameda.net/~ulf/resume.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message ------=_NextPart_000_01D8_01C18E2A.847ADE60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Look, I'm not for flames myself, but I = have to say=20 it gets a whole lot more interesting when there's a forest fire going = on. =20 It's like a Jerry Springer show except it's really quiet.
 
Peter
 
 
----- Original Message -----
From:=20 Robert = L=20 Sowders
Cc: Allen Landsidel ; freebsd-stable@FreeBSD.ORG= ; owner-freebsd-stable@Fre= eBSD.ORG=20 ; Peter/Los Angeles, CA ; = Sam Drinkard = ; sthaug@nethelp.no=20
Sent: Wednesday, December 26, = 2001 3:44=20 PM
Subject: Re: 4.5 PRERELEASE - = Call for=20 testing


This should be = moved to chat,=20 hardware, hackers, you pick it.

Regardless of what the standard says, it has been my = experience that if=20 you have a connection that fails to autoneg to full duplex, then = forcing the=20 freebsd nic to 100 full will result in the expected behavior of a 100 = full=20 connection.  During the negotiation phase the nic says I can only = do 100=20 full and the switch responds with 100 full.

Recent experience with HP-Procurve and = NBase Mega=20 switches confirmed that they continually refused to autoneg 100 full = until the=20 nics were forced to 100 full.  Subsequently turning the nics back = to=20 autoneg produced 100 full connections.  Why this occurred is = beyond me,=20 but after three days of testing that was the fix.

It may be that this is not the experience = of the other=20 readers of this thread.  That's fine, all I'm saying is, if = you're having=20 trouble with full duplex then try forcing the nic to full and see what = happens, it works for me.

This=20 really should be moved off stable now.



Ulf Zimmermann=20 <ulf@Alameda.net>
Sent=20 by: owner-freebsd-stable@FreeBSD.ORG=20

12/26/2001 02:29 PM =
Please respond to ulf

        =
        To: =    =20    "Peter/Los Angeles, CA"=20 <peter@haloflightleader.net>
        cc:       =  Sam=20 Drinkard <sam@wa4phy.net>, Allen Landsidel = <all@biosys.net>,=20 sthaug@nethelp.no, freebsd-stable@FreeBSD.ORG
        Subject: =  =20      Re: 4.5 PRERELEASE - Call for=20 testing


On=20 Wed, Dec 26, 2001 at 02:22:15PM -0800, Peter/Los Angeles, CA = wrote:
>=20 Please correct me if I'm wrong, but isn't it kind of strange = that
>=20 auto-sensing/auto-negotiating must be enabled on both sides for the=20 feature
> to work a bit strange?
>
> At home, I = have a=20 Netgear FS116, a 16-Port unmanaged switch.  It is
>=20 auto-sensing/full-duplex 10/100Mbits/sec switch.  Therefore, we=20 cannot
> control how it will behave.
>
> On the = other hand,=20 I have network cards on my computer which I can set to
>=20 full/half/auto/10/100, whatever combination I like, and yet, the = switch=20 will
> continue to work.
>
> What I'm getting at is = that=20 just because one end is not set to
> auto-negotiate/auto-sense = that=20 there will be no communication at all.  Say,
> that one end = is set=20 manually, and the other end is automatic.  The automatic
> = end will=20 set itself to the parameters of the one that is manually set.=20  This
> is how my network works.  Thus, I don't = believe that=20 both ends, need to be
> set the same way in order to work in = this=20 scenario.
>
> The automatic will automatically=20 negotiate/auto-sense to whatever can't be
> changed, as a = result, they=20 work.  Or is this even what you folks are arguing
> = about?

I=20 do not know if this is written in the standard, but I have seen=20 devices
where if you turn off AutoNeg, they won't respond at all to = the=20 packets.
But I have also seens devices which will still respond, = but just=20 to their
fixed setting. I personal prefer it that if I turn off = autoneg, it=20 won't
do anything, because that gives you a fixed point. Any = production=20 system
I always set switch and host to full 100.

-- =
Regards,=20 = Ulf.

-------------------------------------------------------------= --------
Ulf=20 Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: = 510-865-0204
You can=20 find my resume at: http://seven.Alameda.net/~ulf/resume.html

To = Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe=20 freebsd-stable" in the body of the=20 message


------=_NextPart_000_01D8_01C18E2A.847ADE60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16:32:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 141C137B419 for ; Wed, 26 Dec 2001 16:32:23 -0800 (PST) Received: from mail2.uniserve.com ([204.244.156.10]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 16JOT3-000D5l-00; Wed, 26 Dec 2001 16:32:17 -0800 Date: Wed, 26 Dec 2001 16:32:17 -0800 (PST) From: Tom X-Sender: tom@athena.uniserve.ca To: Allen Landsidel Cc: "Peter/Los Angeles, CA" , Sam Drinkard , sthaug@nethelp.no, freebsd-stable@FreeBSD.ORG Subject: Re: 4.5 PRERELEASE - Call for testing In-Reply-To: <5.1.0.14.0.20011226181401.00ae1ec8@rfnj.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 26 Dec 2001, Allen Landsidel wrote: > >What I'm getting at is that just because one end is not set to > >auto-negotiate/auto-sense that there will be no communication at all. Say, > >that one end is set manually, and the other end is automatic. The automatic > >end will set itself to the parameters of the one that is manually set. This > >is how my network works. Thus, I don't believe that both ends, need to be > >set the same way in order to work in this scenario. > > For auto-negotiation you are absolutely correct. Setting it manually on > just one end is the right way to do it, and often times, the only way to do it. Turning off auto-negotiation on one end, results in disabling auto-negotiation entirely. See the standard. If the your NIC does perform the capabilities negotiation with your switch, auto-negotiation is assumed to be not supported and the switch will default to half-duplex. The speed isn't an issue, as it easy to auto-detect speed. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 16:58:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from CRWdog.demon.co.uk (adsl-216-103-105-71.dsl.snfc21.pacbell.net [216.103.105.71]) by hub.freebsd.org (Postfix) with ESMTP id 1B39737B417 for ; Wed, 26 Dec 2001 16:58:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by CRWdog.demon.co.uk (Postfix) with ESMTP id 197EB3E41; Wed, 26 Dec 2001 16:58:01 -0800 (PST) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Sam Drinkard Cc: stable@FreeBSD.ORG Subject: Re: 4.5 PRERELEASE - Call for testing In-Reply-To: Your message of "Wed, 26 Dec 2001 16:49:45 EST." <3C2A45F9.EBF0C148@vortex.wa4phy.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-1538300369P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 26 Dec 2001 16:58:01 -0800 From: Andy Sparrow Message-Id: <20011227005801.197EB3E41@CRWdog.demon.co.uk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --==_Exmh_-1538300369P Content-Type: text/plain; charset=us-ascii > Well, having followed this thread for some bit, I gotta throw my $.02 > worth in.. I'm one of those who has machines connected via a "dumb" > 10baseT hub, and auto everything doesn't work. I think the whole point > is that a certain amount of knowledge is required *before* one should > attempt to build a network. Both the 4.5-Pre machine as well as the > RH-7 box have identical nic's in them, but alas, *neither one* knows > about the other one. Only a manual configuration of the one in the 4.5 > machine is configurable. RH 7, with same card is not. It's MY dilemma, > and despite all the chit-chat, what do you do when you *can't* configure > a card manually, and it won't auto-negotiate? > > Sam Buy a card that Just Works? ;) I do sympathize - I've got 6 DEC 21x4x-based cards here (two generations of NIC for my home network) that /never/ worked properly with any of my switches regardless of settings, and I struggled with them for ages (I won't tell you what I paid for 'em way back when, but you could buy a respectable desktop for that now), before replacing them with Intel or Kingston cards. Which like, Just Worked @ 100/full "out of the box". No user intervention required. (Unfortunately the Kingston card only worked for 6 weeks before dying totally, but that's a different issue). Personally, I think the Intel 8255x cards rock. They have a lifetime warranty from Intel (I'm told, I've never had one go bad) and second-hand ones are cheaper on Ebay than a new RealTek card. Surplus new ones can sometimes be had for a song too, since they started being OEM'ed. Oh, and they work well with FreeBSD - IIRC, ftp.cdrom.com use(d) this NIC? Cheers, AS --==_Exmh_-1538300369P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.5 07/13/2001 iD8DBQE8KnIYPHh895bDXeQRAntTAJ94Cjqp8IAb5So8TqSUyZ/zGx9FmwCgvoFo nBIY+9qPkdlyHcVM0YizBqA= =MIxe -----END PGP SIGNATURE----- --==_Exmh_-1538300369P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 17:36:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gw-1.adm.msi.ru (gw-1-A1-115k.adm.msi.ru [212.14.192.45]) by hub.freebsd.org (Postfix) with ESMTP id ADA8237B416 for ; Wed, 26 Dec 2001 17:36:08 -0800 (PST) Received: from vperep1 ([212.14.192.97]) by gw-1.adm.msi.ru (8.10.2/8.10.2) with ESMTP id fBRCfPv19520 for ; Thu, 27 Dec 2001 23:41:31 +1100 (MG) Date: Thu, 27 Dec 2001 12:38:31 +1100 From: Vladimir Perepechenko X-Mailer: The Bat! (v1.53d) UNREG / CD5BF9353B3B7091 Reply-To: Vladimir Perepechenko Organization: Magadansvyazinform Company X-Priority: 3 (Normal) Message-ID: <1833336487.20011227123831@adm.msi.ru> To: stable@FreeBSD.ORG Subject: Where can I get (download) Free BSD 2.2.7 Release ? In-Reply-To: <20011015231530.A21091@freeway.dcfinc.com> References: <20011015231530.A21091@freeway.dcfinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=Windows-1251 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Çäðàâñòâóéòå , I couldn/t find it at ftp://ftp.freebsd.org Thank you/ regards, Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 18:31:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from empty1.ekahuna.com (empty1.ekahuna.com [198.144.200.196]) by hub.freebsd.org (Postfix) with ESMTP id 90B9A37B417 for ; Wed, 26 Dec 2001 18:31:35 -0800 (PST) Received: from pc-02 (pc02.ekahuna.com [198.144.200.197]) by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Wed, 26 Dec 2001 18:31:34 -0800 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: stable@FreeBSD.ORG Date: Wed, 26 Dec 2001 18:31:34 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: 4.5 PRERELEASE - Call for testing Reply-To: pjklist@ekahuna.com Message-ID: <3C2A1786.17075.63462D@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 26 Dec 2001, at 12:38, stable-digest boldly uttered: > Date: Wed, 26 Dec 2001 14:00:27 +0100 > From: sthaug@nethelp.no > Subject: Re: 4.5 PRERELEASE - Call for testing > > > > Thus the advice to either use auto-negotiate everywhere, or use manual > > > everywhere. One end auto-negotiate and one end manual is a recipe for > > > disaster. > > > > So, that implies that in these cases non-managable switches are doomed > > as you cannot 'hard-set' them to some value. > > If auto-negotiate fails on non-managable switches, you can usually get > it to work after the fact by manually configuring the box at the other > end. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no Actually that is not always the case. I have a Netgear "auto- sensing" 8-port switch here which, no matter what I do, won't run half-duplex with an Intel 82558-based card, even if the Intel is "locked" at half-duplex. I'm told in this particular case that it has to do with Intel's (Windoze) NIC drivers, who knows. Others in this thread said you need to have both sides manual or both sides auto. I have also seen situations where an HP Procurve switch would not run correctly at 10Mbps/Half with a 3com 3CXFE575BT PC-card NIC, even if BOTH sides were "locked" at that speed. The symptom was very slow communication HP --> 3com, the other direction was OK. At 100Mbps it was fine. (this was also under windoze) There are no shortage of scenarios where auto-negotiation does NOT do what you want, even if just one end is "locked". And sometimes there are even issues when everything is set manually. See below. > Date: Wed, 26 Dec 2001 11:43:29 -0800 (PST) > From: Tom > > I would recommend people use auto everwhere. Even the cheap devices > support it properly now. Auto-negotiation is going to become more > critical as more options are added to the ethernet standard (ie. > master/slave, flow control). The problem with this is that we DON'T always want every link to operate at its "maximum" setting. I have little interest in giving huge chunks of bandwidth to every miscellaneous user (and along with it the ability to do something dumb like bog the whole network down when they accidentally drag their entire hard drive icon to a network drive) when their work amounts to saving a couple of word processing documents to a server each day. Those people don't even need 10Mbps of bandwidth, much less 100 or more. All switches should have configurable ports, IMHO. Phil -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 19:38:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ct980320-b.blmngtn1.in.home.com (ct980320-b.blmngtn1.in.home.com [65.8.207.32]) by hub.freebsd.org (Postfix) with ESMTP id 28BB437B405 for ; Wed, 26 Dec 2001 19:38:37 -0800 (PST) Received: (from mikes@localhost) by ct980320-b.blmngtn1.in.home.com (8.11.6/8.11.4) id fBR3cae00416 for freebsd-stable@freebsd.org; Wed, 26 Dec 2001 22:38:36 -0500 (EST) (envelope-from mikes) From: Mike Squires Message-Id: <200112270338.fBR3cae00416@ct980320-b.blmngtn1.in.home.com> Subject: Uneventful upgrade to 4.5-PRERELEASE #2 To: FreeBSD Stable Date: Wed, 26 Dec 2001 22:38:36 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just finished upgrading from 4.4-STABLE to 4.5-PRERELEASE #2 (via cvsup). I did the buildworld and kernel remotely while at work, and installworld and mergemaster took 21 minutes. So far, nothing unusual to report. samba is running in excess of 4MB/sec which is much better than in earlier versions of 4.x. This is slightly faster than an NT 4 server with essentially the same hardware (but with 2 CPUs and more memory). MLS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 19:57: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from a.mx.carrel.org (darjeeling.carrel.org [216.173.212.202]) by hub.freebsd.org (Postfix) with ESMTP id C1A2737B417 for ; Wed, 26 Dec 2001 19:57:02 -0800 (PST) Received: from irishbreakfast.carrel.org (irishbreakfast.carrel.org [216.173.212.206]) by a.mx.carrel.org (Postfix) with ESMTP id CBBE413894; Wed, 26 Dec 2001 19:56:52 -0800 (PST) Date: Wed, 26 Dec 2001 19:56:55 -0800 Subject: Re: 4.5 PRERELEASE - Call for testing Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v480) Cc: stable@FreeBSD.ORG To: pjklist@ekahuna.com From: William Carrel In-Reply-To: <3C2A1786.17075.63462D@localhost> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.480) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, December 26, 2001, at 06:31 PM, Philip J. Koenig wrote: > The problem with this is that we DON'T always want every link to > operate at its "maximum" setting. > > I have little interest in giving huge chunks of bandwidth to every > miscellaneous user (and along with it the ability to do something > dumb like bog the whole network down when they accidentally drag > their entire hard drive icon to a network drive) when their work > amounts to saving a couple of word processing documents to a server > each day. Those people don't even need 10Mbps of bandwidth, much > less 100 or more. Using switch settings to obtain this sort of configuration/protection is at best crude. Try dummynet(4) and/or some QoS capable network hardware. Or use some reporting software in conjunction to a packet sniffer and levy penalties on those that "abuse" the network. There are lots of approaches that can make this work. Trying to juryrig your switch ports to run in some sort of half-baked mode is definately not the most efficient approach at solving this problem. > All switches should have configurable ports, IMHO. Managed switches aren't for every scenario, particularly when some of us would rather spend $3000 to purchase mountain bikes than network equipment for our home. (Granted the prices are coming down on smaller managed switches, but...) -- wac To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 20:40: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tng.tmn.ru (tngent02.tng.tmn.ru [212.76.168.162]) by hub.freebsd.org (Postfix) with ESMTP id 4CB3537B405 for ; Wed, 26 Dec 2001 20:39:57 -0800 (PST) Received: from tng.tmn.ru [10.28.66.204] by tng.tmn.ru [212.76.168.162] with SMTP (MDaemon.PRO.v4.0.0.R) for ; Thu, 27 Dec 2001 09:39:49 +0500 Message-ID: <3C2AA60B.4070607@tng.tmn.ru> Date: Thu, 27 Dec 2001 09:39:39 +0500 From: "Igor I. Ushatinsky" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.4) Gecko/20011022 X-Accept-Language: ru, en-us MIME-Version: 1.0 To: Vladimir Perepechenko Cc: stable@FreeBSD.ORG Subject: Re: Where can I get (download) Free BSD 2.2.7 Release ? References: <20011015231530.A21091@freeway.dcfinc.com> <1833336487.20011227123831@adm.msi.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MDRemoteIP: 10.28.66.204 X-Return-Path: igor@tng.tmn.ru X-MDaemon-Deliver-To: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Vladimir! > I couldn/t find it at ftp://ftp.freebsd.org You may find 2.1.7.1-RELEASE at ftp://ftp4.ru.freebsd.org/pub/FreeBSD/releases/i386/ /Igor, Russia, Siberia, Tyumen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 20:53:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from haloflightleader.net (adsl-63-197-56-193.dsl.lsan03.pacbell.net [63.197.56.193]) by hub.freebsd.org (Postfix) with ESMTP id 0D1B437B405 for ; Wed, 26 Dec 2001 20:53:05 -0800 (PST) Received: from enterprise ([192.168.1.254]) by haloflightleader.net (8.11.6/8.11.6) with SMTP id fBR4qh907147; Wed, 26 Dec 2001 20:52:43 -0800 (PST) (envelope-from peter@haloflightleader.net) Message-ID: <003501c18e91$fe155ea0$0101a8c0@haloflightleader.net> From: "Peter Ong" To: , "William Carrel" Cc: References: Subject: Re: 4.5 PRERELEASE - Call for testing Date: Wed, 26 Dec 2001 20:50:14 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > All switches should have configurable ports, IMHO. I think all of those Dell rack optimized 8xP4 2GHz, with 8GB of memory should be even cheaper too. I must say as much as I would like to keep a catalyst 2948G at home, it would be nice, but I haven't really had a need to manage at the switch level yet. Not even at work. All ports, except for the servers, run at auto/auto. The servers that I have at home are hand-me-down workstations from previous fortune 500 companies I've worked for. They are 60MHz/40MB, and the 90MHz/52MB. The 60 functions as an email server, and the 90 probably the web server. I haven't decided yet. Both of these machines have a 10Mbits/sec card that won't go faster, and I'm not sure if it's full/half duplex. All I know is I can tranfer 1GB of data to and from these machines simulataneously within 12 to 15 minutes. There are 4 machines total on the network; my laptop, and my old PIII 400/128MB workstation. I burned out the graphics card so it got demoted to server status. Now it's my file server, and it has a 10/100 full/half auto nic by Netgear. I do have a question since we're on this subject. This is probably best suited for another thread or another group altogether but I'll risk it. There are many platforms out there. Intel, Alpha, Macintosh, Sun's machines, SGI, VAX, and a bunch of others whose names I've only heard and read about. But the only real hands-on experience that I have, and that I can call even remotely that I'm knowledgeable on is the Intel platform. I play with these machines every day. From the 386 all the way to the brand new P4s. The P4s are really fast, and I like them; very powerful. I bet if I get a chance to put FBSD on them aside from my company mandated NT4, it would show some serious performance no one expected possible of the machine. The question that I have is that Pentium 4, running at some 2GHz, are nice, and fast. If it was coupled with 1 or 2 GB of memory it would be a really smoking machine. Now, I look at SGI, and their machines that use their own CPU run at some 500 to 600 MHz, and yet they are so much more expensive than Intel machines. Are they really that much more powerful than Intel CPUs that they are worth the extra money? For what uses might this extra power be needed? I've worked in two Fortune 500 companies. I've seen their infrastructure on the backend, but it isn't using these high-end exotic hardware. They mostly use PIII 800s with Cat 1900/2900s on NT4. This was within the past 3 years. In the lawfirm I work for now, they are using a similar setup. I've never really seen any of these corps embrace Linux/BSD/Unix. I forgot to mention Novell, they're there too more than Unix has a presence. Maybe I don't know the capabilities of these other hardwares, but from what I know, Intel machines are plenty sufficient even for heavy loads. Those Dell Poweredges are pretty sweet machines. We use the 2400SCs at this lawfirm, and not only are they rock solid stable, but they are heavy as semi-trucks too. Good for theft deterence. The other Fortune 500 company used rack optimized PowerEdges, and the other one used nothing but Dell Latitude as standard issue to their company constituents (you gotta give it back if you leave the company). I also worked for an ISP which used nothing but "white box" home made in the office with AMD K6-2 chips all running on RH/Linux. This ISP was a nationwide ISP that served DSL, worked great. It was moving a ton of pornomail everyday via sendmail on one or two of these K6-2 machines (500 - 600MHz/128MB). > Managed switches aren't for every scenario, particularly when some of us > would rather spend $3000 to purchase mountain bikes than network > equipment for our home. (Granted the prices are coming down on smaller > managed switches, but...) Since we're talking about wish lists... New surfboard (1 long board and 1 short board) want a box of wax too. New amplifier and a Gibson Les Paul (box of picks and strings 0.9s) Volkswagon Passat Blue Silver Dell 2400SC P4 2GHz 2GB memory with Perc Module Cisco 3600 Router And an OC3 connection to my one bedroom apartment. Santa disappointed me big time this year. And I'm not even asking him for ponies anymore. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 21: 1:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hawk.prod.itd.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id EB1F237B416; Wed, 26 Dec 2001 21:01:00 -0800 (PST) Received: from user-33qsdcu.dialup.mindspring.com ([199.174.53.158] helo=hole2) by hawk.prod.itd.earthlink.net with smtp (Exim 3.33 #1) id 16JSf1-0002a4-00; Wed, 26 Dec 2001 21:00:56 -0800 Message-ID: <001201c18e93$ef95e780$0100a8c0@hole2> From: "Doug Welch" To: "Peter/Los Angeles, CA" , "John Hanley" , "Keith J" Cc: "Tom" , , References: <20011227002248.40200.qmail@web10104.mail.yahoo.com> <01cf01c18e6d$59b81420$245b1486@hhlaw.com> Subject: Re: 4.5 PRERELEASE - Call for testing Date: Wed, 26 Dec 2001 23:04:14 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry to intrude but these are the results of real transfers using : auto and auto, then auto and manual ftp> mget fasttimesatridgemont.avi local: fasttimesatridgemont.avi remote: fasttimesatridgemont.avi 150 Opening BINARY mode data connection for 'fasttimesatridgemont.avi' (682295296 bytes). 100% |*************************************************************************** *******************************| 650 MB 00:00 ETA 226 Transfer complete. 682295296 bytes received in 126.71 seconds (5.14 MB/s) $ ifconfig dc0 dc0: flags=8843 mtu 1500 inet 192.168.0.25 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::220:78ff:fe07:9b15%dc0 prefixlen 64 scopeid 0x1 ether 00:20:78:07:9b:15 media: Ethernet autoselect (100baseTX ) status: active ########### Above NIC located on freeBSD 4.5 release workstation $ ifconfig dc0 dc0: flags=8843 mtu 1500 media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.0.15 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::220:78ff:fe03:85e8%dc0 prefixlen 64 scopeid 0x1 inet 192.168.0.15 255.255.255.0 NONE media autoselect <------------- set to auto *********** Above NIC located on OpenBSD 3.0 current server Then on the server side of things.... I edited hostname.dc0 and changed the entry to: inet 192.168.0.27 255.255.255.0 NONE media 100baseTX mediaopt full-duplex <------------set to manual now Then saved the changes and rebooted. I did this instead of just changing on the fly for safety sake and a clean test. $ ifconfig dc0 dc0: flags=8843 mtu 1500 media: Ethernet 100baseTX full-duplex <-----no auto here anymore status: active inet 192.168.0.15 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::220:78ff:fe03:85e8%dc0 prefixlen 64 scopeid 0x1 ********** Above is after reboot I verified /etc/hostname.dc0 was still reflecting my change.. ftp> prompt Interactive mode off. ftp> mget fasttimesatridgemont.avi local: fasttimesatridgemont.avi remote: fasttimesatridgemont.avi 150 Opening BINARY mode data connection for 'fasttimesatridgemont.avi' (682295296 bytes). 100% |*************************************************************************** *******************************| 650 MB 00:00 ETA 226 Transfer complete. 682295296 bytes received in 125.96 seconds (5.17 MB/s) So... 682295296 bytes received in 126.71 seconds (5.14 MB/s) << this was both nics set to auto 682295296 bytes received in 125.96 seconds (5.17 MB/s) << this was after manual change of server nic ?????? After two years as a Adm on a broadband network I leaned not to trust any vendor docs without testing first. Sorry again, But I am glad Peter's initial issue was solved . Right or wrong I see no diff here except manual was a fraction faster. If I am wrong and I am quite frequently or I have miss understood this auto issue sorry for the spam... -dw ----- Original Message ----- From: "Peter/Los Angeles, CA" To: "John Hanley" ; "Keith J" Cc: "Tom" ; ; Sent: Wednesday, December 26, 2001 6:27 PM Subject: Re: 4.5 PRERELEASE - Call for testing > No!!! We must continue the revolution!!! Welcome to the revolution!!! > AAAAHHH!!! Auto-neg/Auto-sense should be the only subject in this list for > the next 10 years until we resolve this issue. > > Continue the fight laddies!!! Arrgggh!!! Fight for your right to > auto-negotiate. > > > Peter > > PS > Was just kidding. I started this thread, but it was just about a Samba > problem that didn't even have anything to do with layer 2 devices. Anyway, > like I've posted before, the problem was solved, and the culprits were on > the application layer, not the data link. No animals were harmed in the > creation of this email. > > ----- Original Message ----- > From: "John Hanley" > To: "Keith J" > Cc: "Tom" ; ; > Sent: Wednesday, December 26, 2001 4:22 PM > Subject: Re: 4.5 PRERELEASE - Call for testing > > > > --- Keith J wrote: > > > Well gee Tom.... if one end doesn't respond to negotiation... are you > > > saying the smart end will force a speed or duplex that can't possibly > > > work? Lets say I have an old 10Mbs ONLY card... are you declaring > > > that it gets toasted by auto-negotiate every single time? > > > > OK, this is boring. Debating opinions is occasionally useful, > > but facts are facts and flamage won't change them. Please let > > Cisco have the last word on this topic: > > > > http://www.cisco.com/warp/public/473/46.html > > > > Per the IEEE 802.3u specification, it not possible to manually > > configure one link partner for 100 Mbps full-duplex and still > > autonegotiate to full-duplex with the other link partner. > > Attempting to configure one link partner for 100 Mbps full-duplex > > and the other link partner for auto-negotiation will result in a > > duplex mismatch. This is a result of one link partner auto-negotiating > > and not seeing any auto-negotiation parameters from the other link > > partner and defaulting to half-duplex. > > > > __________________________________________________ > > Do You Yahoo!? > > Send your FREE holiday greetings online! > > http://greetings.yahoo.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 21:13:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id A6E6837B405 for ; Wed, 26 Dec 2001 21:13:34 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id fBR5DUq45681; Wed, 26 Dec 2001 21:13:30 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id fBR5DUr06388; Wed, 26 Dec 2001 21:13:30 -0800 (PST) (envelope-from jdp) Date: Wed, 26 Dec 2001 21:13:30 -0800 (PST) Message-Id: <200112270513.fBR5DUr06388@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: insane@oneinsane.net Subject: Re: private cvsup In-Reply-To: <15402.11927.3985.142103@witchblade.saic.com> References: <15402.11927.3985.142103@witchblade.saic.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <15402.11927.3985.142103@witchblade.saic.com>, Ron Rosson wrote: > I am running a FreeBSD server that has the cvsup-mirror installed > and is maintaing a copy of "The FreeBSD Tree". Now we are finding > that we need to keep a private copy of OpenBSD as well. > > Is there a way for a FreeBSD server to givess access to OpenBSD and > FreeBSD's source tree via CVSUP from the same machine. If so how > could this be accomplished. It's not hard to do. Just create collections for the OpenBSD sources as described in cvsupd(8). Or, look at the existing server config files for the FreeBSD sources and modify them appropriately. You can put the new config files in with the FreeBSD ones, or better yet, use cvsupd's "-c" option to segregate them into a separate directory. For example: cvsupd ... -c sup:sup.local ... John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 21:30:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from empty1.ekahuna.com (empty1.ekahuna.com [198.144.200.196]) by hub.freebsd.org (Postfix) with ESMTP id A823C37B419 for ; Wed, 26 Dec 2001 21:30:20 -0800 (PST) Received: from pc-02 (pc02.ekahuna.com [198.144.200.197]) by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com; Wed, 26 Dec 2001 21:30:20 -0800 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: stable@FreeBSD.ORG Date: Wed, 26 Dec 2001 21:30:20 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: 4.5 PRERELEASE - Call for testing Reply-To: pjklist@ekahuna.com Cc: William Carrel Message-ID: <3C2A416C.12065.106F4F3@localhost> References: <3C2A1786.17075.63462D@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 26 Dec 2001, at 19:56, William Carrel boldly uttered: > On Wednesday, December 26, 2001, at 06:31 PM, Philip J. Koenig wrote: > > > The problem with this is that we DON'T always want every link to > > operate at its "maximum" setting. > > > > I have little interest in giving huge chunks of bandwidth to every > > miscellaneous user (and along with it the ability to do something > > dumb like bog the whole network down when they accidentally drag > > their entire hard drive icon to a network drive) when their work > > amounts to saving a couple of word processing documents to a server > > each day. Those people don't even need 10Mbps of bandwidth, much > > less 100 or more. > > Using switch settings to obtain this sort of configuration/protection is > at best crude. Try dummynet(4) and/or some QoS capable network > hardware. The switches and NICs for many years already should have the inherent ability to run locked at 10Mbps. Indeed they push this as a "feature". Why should I go spend outrageous sums on overpriced "QoS" hardware or install an entirely new box for this purpose when the existing switches and NICs should already do what I need? > Or use some reporting software in conjunction to a packet > sniffer and levy penalties on those that "abuse" the network. > There are lots of approaches that can make this work. Trying to juryrig your > switch ports to run in some sort of half-baked mode is definately not > the most efficient approach at solving this problem. One thing I have learned over the years is the advantage of treating users like herding cats. It is far more useful to simply make resources unavailable to users that will abuse them than to try and "discipline" them if they do. Keeps down the personal problems, reduces political problems, minimizes the ulcers, and works a lot more reliably too. > > All switches should have configurable ports, IMHO. > > Managed switches aren't for every scenario, particularly when some of us > would rather spend $3000 to purchase mountain bikes than network > equipment for our home. (Granted the prices are coming down on smaller > managed switches, but...) Not really talking about home networks, but since you brought it up: I have 2 switches in my home network - a main HP Procurve and a small Netgear. I want to set a particular workstation (using a common Intel NIC) to half-duplex which is connected to the Netgear - no can do. Having to go out and spend $500 on a switch whose ports can be manually locked instead of $100 on the Netgear seems a bit excessive considering the cost of adding such functionality. (I know, each of those 8 switches costs $0.43) Phil -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 26 23:19:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id DC6D337B405; Wed, 26 Dec 2001 23:19:39 -0800 (PST) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.34 #1) id 16JUp7-0004np-00; Thu, 27 Dec 2001 09:19:29 +0200 Received: from localhost ([127.0.0.1] helo=pampa.cs.huji.ac.il ident=danny) by pampa.cs.huji.ac.il with esmtp (Exim 3.22 #2) id 16JUp5-0002FR-00; Thu, 27 Dec 2001 09:19:27 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: sos@freebsd.dk Cc: Matthew Gilbert , Matthew Dillon , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, danny@cs.huji.ac.il Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers In-Reply-To: Message from S ren Schmidt of "Thu, 27 Dec 2001 00:15:56 +0100." <200112262315.fBQNFue42555@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 27 Dec 2001 09:19:27 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > It seems Matthew Gilbert wrote: > > > So, general question to everyone having crashes during heavy > > > IDE workloads: Please post your /var/run/dmesg.boot > > > output. > = > > atapci0: port 0xd000-0xd00f at device = 7.1 on = > = > You have the VIA 82c686b southbridge chip which is known to cause sever= e > data corruption problems if the BIOS does not setup the northbidge > chip correctly. Please check with your board vendor if they have a > new updated BIOS that fixes this problem. [...] S=F8ren, I have an AOpen MB, and I just read all their fixes, but none seem to relate to the VIA 82c686b problem, is there, or could there be a list of OK Bios/MB? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 0:30:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hugo10.ka.punkt.de (kagate.punkt.de [194.77.232.254]) by hub.freebsd.org (Postfix) with ESMTP id 09E0D37B416 for ; Thu, 27 Dec 2001 00:30:48 -0800 (PST) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.11.4/8.11.4) id fBR8Ufn74317; Thu, 27 Dec 2001 09:30:41 +0100 (CET) (envelope-from ry93) From: "Patrick M. Hausen" Message-Id: <200112270830.fBR8Ufn74317@hugo10.ka.punkt.de> Subject: Re: RELENG_4_5 In-Reply-To: <20011226164233.R1494@shell.gsinet.sittig.org> To: Gerhard Sittig Date: Thu, 27 Dec 2001 09:30:41 +0100 (CET) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL92 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all! Gerhard Sittig wrote: > On Wed, Dec 26, 2001 at 15:01 +0100, Patrick M. Hausen wrote: > > > > Just a minor question: at which point in the 4.5 release cycle > > will a RELENG_4_5 tag appear? > > Apparently when release 4.5 *did* appear. That's how things were > designed and done up to now. :) Got it. Thanks, folks. Regards, Patrick M. Hausen Technical Director -- punkt.de GmbH Internet - Dienstleistungen - Beratung Scheffelstr. 17 a Tel. 0721 9109 -0 Fax: -100 76135 Karlsruhe http://punkt.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 1:38:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 9A61137B405; Thu, 27 Dec 2001 01:38:29 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id fBR9cOQ95619; Thu, 27 Dec 2001 10:38:24 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200112270938.fBR9cOQ95619@freebsd.dk> Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers In-Reply-To: <200112270001.fBR01Ns48341@apollo.backplane.com> To: Matthew Dillon Date: Thu, 27 Dec 2001 10:38:24 +0100 (CET) Cc: Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Matthew Dillon wrote: > Sorry, I meant I'd follow up with Matthew Gilbert. Also, I've > been trying to track down a crash in nfs_node that Nils Holland > has been having - he appears to have the same chipset and could > have the same problem, and he can reproduce the panic very consistently > within a few hours. > > Brady has an older chipset. Are there any known problems with this > chipset? Nope... > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xe400-0xe40f at device 7.1 on pci0 -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 1:45:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id CCFFE37B417; Thu, 27 Dec 2001 01:45:05 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id fBR9j1e97273; Thu, 27 Dec 2001 10:45:01 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200112270945.fBR9j1e97273@freebsd.dk> Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers In-Reply-To: <200112262355.fBQNtfK48250@apollo.backplane.com> To: Matthew Dillon Date: Thu, 27 Dec 2001 10:45:01 +0100 (CET) Cc: Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Matthew Dillon wrote: > Soren, if you post a patch for 4.x I will be happy to follow-up > with Brady. I've been working with Brady for several days now trying > to track down corruption in the vm_page array. I *really* want to know > if a VIA chipset patch solves his problem, because it would > also explain about a dozen similar bug reports over the last 6 months. > (Which would also be good backing to get it into 4.5). OK, here goes the VIA 686b patch, it is hand cut out from the bulk patches to go into 4.5 so beware :) Index: ata-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.50.2.27 diff -u -r1.50.2.27 ata-all.c --- ata-all.c 22 Dec 2001 19:12:18 -0000 1.50.2.27 +++ ata-all.c 25 Dec 2001 14:21:31 -0000 @@ -240,6 +235,30 @@ return 0; } +static void +ata_via686b(device_t dev) +{ + device_t *children, child; + int nchildren, i; + + if (device_get_children(device_get_parent(dev), &children, &nchildren)) + return; + + for (i = 0; i < nchildren; i++) { + child = children[i]; + + if (pci_get_devid(child) == 0x03051106 || /* VIA KT133 */ + pci_get_devid(child) == 0x03911106) { /* VIA KX133 */ + pci_write_config(child, 0x75, 0x83, 1); + pci_write_config(child, 0x76, + (pci_read_config(child, 0x76, 1) & 0xdf) | 0xd0,1); + device_printf(dev, "VIA '686b southbridge fix applied\n"); + break; + } + } + free(children, M_TEMP); +} + static const char * ata_pci_match(device_t dev) { @@ -474,9 +519,24 @@ } break; - case 0x05711106: - case 0x74111022: - case 0x74091022: /* VIA 82C586, '596, '686 & AMD 756, 766 default setup */ + case 0x05711106: /* VIA 82C586, '596, '686 default setup */ + + /* prepare for ATA-66 on the 82C686a and rev 0x12 and newer 82C596's */ + if ((ata_find_dev(dev, 0x06861106, 0) && + !ata_find_dev(dev, 0x06861106, 0x40)) || + ata_find_dev(dev, 0x05961106, 0x12)) { + pci_write_config(dev, 0x50, + pci_read_config(dev, 0x50, 4) | 0x030b030b, 4); + } + + /* the '686b might need the data corruption fix */ + if (ata_find_dev(dev, 0x06861106, 0x40)) + ata_via686b(dev); + + /* FALLTHROUGH */ + + case 0x74091022: /* AMD 756 default setup */ + case 0x74111022: /* AMD 766 default setup */ /* set prefetch, postwrite */ pci_write_config(dev, 0x41, pci_read_config(dev, 0x41, 1) | 0xf0, 1); @@ -495,14 +555,6 @@ /* set sector size */ pci_write_config(dev, 0x60, DEV_BSIZE, 2); pci_write_config(dev, 0x68, DEV_BSIZE, 2); - - /* prepare for ATA-66 on the 82C686a and rev 0x12 and newer 82C596's */ - if ((ata_find_dev(dev, 0x06861106, 0) && - !ata_find_dev(dev, 0x06861106, 0x40)) || - ata_find_dev(dev, 0x05961106, 0x12)) { - pci_write_config(dev, 0x50, - pci_read_config(dev, 0x50, 4) | 0x030b030b, 4); - } break; case 0x10001042: /* RZ 100? known bad, no DMA */ -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 1:47: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 618F837B405; Thu, 27 Dec 2001 01:46:56 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id fBR9kln97712; Thu, 27 Dec 2001 10:46:47 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200112270946.fBR9kln97712@freebsd.dk> Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers In-Reply-To: To: Danny Braniss Date: Thu, 27 Dec 2001 10:46:47 +0100 (CET) Cc: Matthew Gilbert , Matthew Dillon , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Danny Braniss wrote: > > It seems Matthew Gilbert wrote: > > > > So, general question to everyone having crashes during heavy > > > > IDE workloads: Please post your /var/run/dmesg.boot > > > > output. > > > > > atapci0: port 0xd000-0xd00f at device 7.1 on > > > > You have the VIA 82c686b southbridge chip which is known to cause severe > > data corruption problems if the BIOS does not setup the northbidge > > chip correctly. Please check with your board vendor if they have a > > new updated BIOS that fixes this problem. > [...] > > Søren, > I have an AOpen MB, and I just read all their fixes, but none > seem to relate to the VIA 82c686b problem, is there, or could there be > a list of OK Bios/MB? Not that I know of, most serious vendors list the 686b problem in on of their updates, but some only engages it if they also find a SB live! card in the system since that really breaks :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 1:50:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gscamnlm03.wr.usgs.gov (gscamnlm03.wr.usgs.gov [130.118.4.113]) by hub.freebsd.org (Postfix) with ESMTP id CCDC037B405; Thu, 27 Dec 2001 01:50:10 -0800 (PST) To: Tom Cc: Allen Landsidel , freebsd-stable@FreeBSD.ORG, owner-freebsd-stable@FreeBSD.ORG, "Peter/Los Angeles, CA" , Sam Drinkard , sthaug@nethelp.no Subject: Re: 4.5 PRERELEASE - Call for testing MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Robert L Sowders" Date: Thu, 27 Dec 2001 01:50:07 -0800 X-MIMETrack: Serialize by Router on gscamnlm03/SERVER/USGS/DOI(Release 5.0.8 |June 18, 2001) at 12/27/2001 01:50:10 AM, Serialize complete at 12/27/2001 01:50:10 AM Content-Type: multipart/alternative; boundary="=_alternative 0036085F88256B2F_=" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multipart message in MIME format. --=_alternative 0036085F88256B2F_= Content-Type: text/plain; charset="us-ascii" Not true, nada. I've proved this over and over again. Let's agree to disagree and just move on. Tom Sent by: owner-freebsd-stable@FreeBSD.ORG 12/26/2001 04:22 PM To: "Peter/Los Angeles, CA" cc: Sam Drinkard , Allen Landsidel , sthaug@nethelp.no, freebsd-stable@FreeBSD.ORG Subject: Re: 4.5 PRERELEASE - Call for testing On Wed, 26 Dec 2001, Peter/Los Angeles, CA wrote: > Please correct me if I'm wrong, but isn't it kind of strange that > auto-sensing/auto-negotiating must be enabled on both sides for the feature > to work a bit strange? It isn't strange at all. During auto-negotation both ends exchange a list of capabilities that they support, and they decide what capabilities to enable. If you disable auto-negotiate at one end, the end still doing auto-negotiating will default to half-duplex. The speed is only thing that can automaticatically detected. ... > On the other hand, I have network cards on my computer which I can set to > full/half/auto/10/100, whatever combination I like, and yet, the switch will > continue to work. Not the duplex settings. If you disable auto-negotiating on your NIC, by forcing it to full-duplex, your auto-negotiating switch won't know what you support and default to half-duplex. If the duplex is mistmatched, everything seems to work, but there will be a 1 to 7% packet loss. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message --=_alternative 0036085F88256B2F_= Content-Type: text/html; charset="us-ascii"
Not true, nada.  I've proved this over and over again.  Let's agree to disagree and just move on.



Tom <tom@uniserve.com>
Sent by: owner-freebsd-stable@FreeBSD.ORG

12/26/2001 04:22 PM

       
        To:        "Peter/Los Angeles, CA" <peter@haloflightleader.net>
        cc:        Sam Drinkard <sam@wa4phy.net>, Allen Landsidel <all@biosys.net>, sthaug@nethelp.no, freebsd-stable@FreeBSD.ORG
        Subject:        Re: 4.5 PRERELEASE - Call for testing



On Wed, 26 Dec 2001, Peter/Los Angeles, CA wrote:

> Please correct me if I'm wrong, but isn't it kind of strange that
> auto-sensing/auto-negotiating must be enabled on both sides for the feature
> to work a bit strange?

 It isn't strange at all.  During auto-negotation both ends exchange a
list of capabilities that they support, and they decide what capabilities
to enable.  If you disable auto-negotiate at one end, the end still doing
auto-negotiating will default to half-duplex.  The speed is only thing
that can automaticatically detected.

...
> On the other hand, I have network cards on my computer which I can set to
> full/half/auto/10/100, whatever combination I like, and yet, the switch will
> continue to work.

 Not the duplex settings.  If you disable auto-negotiating on your NIC,
by forcing it to full-duplex, your auto-negotiating switch won't know what
you support and default to half-duplex.  If the duplex is mistmatched,
everything seems to work, but there will be a 1 to 7% packet loss.


Tom


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message

--=_alternative 0036085F88256B2F_=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 2:10:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id 66F4B37B416 for ; Thu, 27 Dec 2001 02:10:24 -0800 (PST) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id fBRAALq05035; Thu, 27 Dec 2001 11:10:21 +0100 (MET) Received: from hyperion.informatik.rwth-aachen.de (hyperion.Informatik.RWTH-Aachen.DE [137.226.194.33]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id fBRAALv05031; Thu, 27 Dec 2001 11:10:21 +0100 (MET) Received: from margaux.informatik.rwth-aachen.de (margaux.Informatik.RWTH-Aachen.DE [137.226.194.72]) by hyperion.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1) with ESMTP id LAA00811; Thu, 27 Dec 2001 11:09:13 +0100 (MET) Received: (from stolz@localhost) by margaux.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1-gb-2) id LAA10176; Thu, 27 Dec 2001 11:10:21 +0100 (MET) Date: Thu, 27 Dec 2001 11:10:21 +0100 From: Volker Stolz To: Matthew Dillon Cc: stable@freebsd.org Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers Message-ID: <20011227111021.A10171@i2.informatik.rwth-aachen.de> References: <200112202333.fBKNXZ679605@apollo.backplane.com> <29650.193.88.88.10.1008956812.squirrel@webmail.jkkn.net> <200112211930.fBLJUs988388@apollo.backplane.com> <200112261924.fBQJORF47150@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <200112261924.fBQJORF47150@apollo.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In local.freebsd-stable, you wrote: > Well, I'm close to being stuck folks. I've looked at 5 of Brady's > core dumps and one of Nils and it appears to be semi-random > corruption of structures that simply cannot be otherwise corrupted > in the way they are being corrupted. The only common thread here is > that Brady and Nils and most of the other people reporting > these crashes have heavy IDE workloads. They also both have > VIA chipsets (different versions though). My Gigabyte 6BXD has Intel's BX chipset. But yesterday it threw up with 'panic: ufsdirrehash'(?) instead of a general page fault, but I didn't reach the console in time to prevent an auto- matic reboot and get the full message :-/ I'll post the dmesg as soon as I get home. -- Wonderful \hbox (0.80312pt too nice) in paragraph at lines 16--18 Volker Stolz * stolz@i2.informatik.rwth-aachen.de Please use PGP or S/MIME for correspondence! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 3:27: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.caravan.ru (mx1.caravan.ru [217.23.130.2]) by hub.freebsd.org (Postfix) with ESMTP id B902137B405 for ; Thu, 27 Dec 2001 03:26:58 -0800 (PST) Received: from virscan (helo=virscan.caravan.ru) by mx1.caravan.ru with drweb-scanned (Exim 3.33 #2) id 16JYgY-000FLm-00; Thu, 27 Dec 2001 14:26:54 +0300 X-ScreenMboxSeparator: From mag@caravan.ru Thu Dec 27 14:26:54 2001 Received: from mag.caravan.ru ([217.23.130.98] helo=caravan.ru) by mx1.caravan.ru with esmtp (Exim 3.33 #2) id 16JYgY-000FLc-00; Thu, 27 Dec 2001 14:26:54 +0300 Message-ID: <3C2B05D2.7020708@caravan.ru> Date: Thu, 27 Dec 2001 14:28:18 +0300 From: Alexey G Misurenko Reply-To: mag@caravan.ru Organization: ISP Caravan User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.6) Gecko/20011130 X-Accept-Language: en-us MIME-Version: 1.0 To: Matthew Dillon , freebsd-stable@freebsd.org Subject: nfs Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Envelope-To: dillon@apollo.backplane.com, freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello! We found one more strange think In documantation to rpc.umntall, " DESCRIPTION rpc.umntall is as command as proposed in the NFS RPC specification; see NFS Version 3 Protocol Specification, RFC 1813, Appendix I. It uses remote procedure calls to remove mount entries from /var/db/mountdtab on the remote NFS server. It is called automatically without any parameters during startup and shutdown of the system. This ensures that showmount(8) does not display old and expired entries. The rpc.umntall command is only needed on client side, where mount_nfs(8) adds a mount entry with the current date to /var/db/mounttab, and umount(8) removes the entry again. The rpc.umntall command cares about all remaining entries in this table which result from crashes or unproper shutdowns. " but if analize /etc/rc* scripts we can see that *rpc.umntall* is called on network_pass3 which is called after the nfsclient allready mount fs exported by nfs server. And we think that this is problems when nfs client return online after crash. Because in this case nfs server don't know any think about crash event of its client. p.s. sorry for badly english -- WBR, Alexey G Misurenko ( MAG-RIPE | MMAGG-RIPN ) Tech. Director of Caravan ISP http://www.caravan.ru Phone: +7 095 3632252 Cell: +7 901 7450163 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 4:15:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.jazz-sax.com (adsl-64-163-65-116.dsl.snfc21.pacbell.net [64.163.65.116]) by hub.freebsd.org (Postfix) with ESMTP id 71D0937B417 for ; Thu, 27 Dec 2001 04:15:36 -0800 (PST) Received: from jazz-sax.com (adsl-64-163-65-114.dsl.snfc21.pacbell.net [64.163.65.114]) by freebsd.jazz-sax.com (8.11.6/8.9.3) with ESMTP id fBR6YvE26467 for ; Wed, 26 Dec 2001 22:34:57 -0800 (PST) (envelope-from ericdano@jazz-sax.com) Message-ID: <3C2ABF4A.50700@jazz-sax.com> Date: Wed, 26 Dec 2001 22:27:22 -0800 From: Eric Dannewitz Reply-To: ericdano@jazz-sax.com Organization: Jazz-Sax User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.7+) Gecko/20011220 X-Accept-Language: en,pdf MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: CVSup problem -- nevermind Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Must have been something with my source tree. Deleteing it all and CVSuping again fixed it.......... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 4:15:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.jazz-sax.com (adsl-64-163-65-116.dsl.snfc21.pacbell.net [64.163.65.116]) by hub.freebsd.org (Postfix) with ESMTP id 4C29937B419 for ; Thu, 27 Dec 2001 04:15:37 -0800 (PST) Received: from jazz-sax.com (adsl-64-163-65-114.dsl.snfc21.pacbell.net [64.163.65.114]) by freebsd.jazz-sax.com (8.11.6/8.9.3) with ESMTP id fBR5UsE11463 for ; Wed, 26 Dec 2001 21:30:54 -0800 (PST) (envelope-from ericdano@jazz-sax.com) Message-ID: <3C2AB046.3010700@jazz-sax.com> Date: Wed, 26 Dec 2001 21:23:18 -0800 From: Eric Dannewitz Reply-To: ericdano@jazz-sax.com Organization: Jazz-Sax User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.7+) Gecko/20011220 X-Accept-Language: en,pdf MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Error compiling a Dual Kernel in latest CVSup? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm getting the following when I try to rebuild my kernel from the latest cvsup. My DUALKERNEL file is the same as the GENERIC with the difference being the lines for dual processor support enabled. Any insight would be helpful. Thanks! install -c -o root -g wheel -m 555 aac.ko /modules/ ===> asr install -c -o root -g wheel -m 555 asr.ko /modules/ ===> bktr ===> bktr/bktr install -c -o root -g wheel -m 555 bktr.ko /modules/ ===> bktr/bktr_mem install -c -o root -g wheel -m 555 bktr_mem.ko /modules/ ===> ciss install -c -o root -g wheel -m 555 ciss.ko /modules/ *** Error code 71 Stop in /usr/src/sys/modules/ciss. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys/compile/DUALKERNEL. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 4:58:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 9CA7237B416 for ; Thu, 27 Dec 2001 04:58:35 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBRCwNF18065; Thu, 27 Dec 2001 13:58:23 +0100 (CET) (envelope-from wkb) Date: Thu, 27 Dec 2001 13:58:23 +0100 From: Wilko Bulte To: R Paschal Cc: Nils Holland , freebsd-stable@FreeBSD.ORG Subject: Re: 4.5-PRERELEASE announcement ? Message-ID: <20011227135823.B17992@freebie.xs4all.nl> References: <3.0.5.32.20011226064544.0095fa00@mail.tucson1.az.home.com> <20011225205928.C29819@freeway.dcfinc.com> <20011226162135.A2481@tisys.org> <3.0.5.32.20011226172225.00959530@mail.tucson1.az.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3.0.5.32.20011226172225.00959530@mail.tucson1.az.home.com>; from rpsbsd@home.com on Wed, Dec 26, 2001 at 05:22:25PM +0000 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 26, 2001 at 05:22:25PM +0000, R Paschal wrote: > At 04:21 PM 12/26/01 +0100, Nils Holland wrote: > >On Wed, Dec 26, 2001 at 06:45:44AM +0000, R Paschal stood up and spoke: > >> > >> Can the general project release announcements be posted into the newsgroup > >> comp.unix.bsd.freebsd.announce? The only thing that I've seen posted there > >> for a long time is the new ports added/updated by Wolfram Schneider. > > > >I guess the official announcement place is the -announce mailing list, and > >indeed, I guess mailing lists have a few advantages over newsgroups. I > >guess it really shouldn't be a problem for people who want to be informated > >about new releases to subscribe to that mailing list. On the other hand, > >it surely wouldn't hurt to forward announcements to the newsgroup, > >although I would suggest anybody who's serious about this to subscribe to > >the mailing list. > > >From personal experience, I see one major problem with that. > > There are a lot of people using ISPs with, for what-ever reason, > misconfigured mail servers. There's not anything they can do about it, > either. > > I know, because I was in that position from Dec. 11, 2000, to mid Aug. 19, > 2001. The ISP I used, ultrasw.com, mapped all their clients mail to one IP > address. When a reverse DNS lookup was done on the IP address, the name > returned was the alphabetically first in the list. But not anymore! > > They now support no reverse lookups. You can try it yourself if you don't > believe it. Do a whois or nslookup on ultrasw.com and then do a reverse > DNS lookup on their DNS server, ns1.ultrasw.com, 204.17.51.1. Then look up > their mail server, mail.ultrasw.com and get its IP, 66.181.240.7 and do a > reverse DNS lookup on it. You can ping them. You can find them at > www.ultrasw.com and see what business they're in. > > Can anybody on that ISP subscribe, post questions, or submit PRs? I don't > think so. They can, however read the newsgroups. They can do something else as well: find an ISP who has a clue. > What do you suppose they think of the mailing list anti-spam policies, > especially after visiting > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html, > which makes no mention of this policy, and they get a cryptic response from > freebsd.org? BTW, from what I saw in questions the last few months, that > policy doesn't do much to stop spam. The FreeBSD postmaster would disagree on that statement I'm sure. -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 5: 3:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id B092E37B41A; Thu, 27 Dec 2001 05:03:12 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBRD33V18115; Thu, 27 Dec 2001 14:03:03 +0100 (CET) (envelope-from wkb) Date: Thu, 27 Dec 2001 14:03:03 +0100 From: Wilko Bulte To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: Matthew Gilbert , Matthew Dillon , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers Message-ID: <20011227140303.C17992@freebie.xs4all.nl> References: <200112262315.fBQNFue42555@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200112262315.fBQNFue42555@freebsd.dk>; from sos@freebsd.dk on Thu, Dec 27, 2001 at 12:15:56AM +0100 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 27, 2001 at 12:15:56AM +0100, Søren Schmidt wrote: > It seems Matthew Gilbert wrote: > > > So, general question to everyone having crashes during heavy > > > IDE workloads: Please post your /var/run/dmesg.boot > > > output. > > > atapci0: port 0xd000-0xd00f at device 7.1 on > > You have the VIA 82c686b southbridge chip which is known to cause severe Hi Soren, isn't it possible to identify the southbridge as a B variant directly? What I mean is, I have an older (non-B) isab0: at device 4.0 on pci0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 pci0 and the strings that is displayed is almost the same (ATA100 versus ATA66). Identifying it a bit more clearly might save a bunch of questions on the lists. Wilko -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 5: 7:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 80B0C37B41A; Thu, 27 Dec 2001 05:07:30 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id fBRD7Ma47234; Thu, 27 Dec 2001 14:07:22 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200112271307.fBRD7Ma47234@freebsd.dk> Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers In-Reply-To: <20011227140303.C17992@freebie.xs4all.nl> To: Wilko Bulte Date: Thu, 27 Dec 2001 14:07:22 +0100 (CET) Cc: Matthew Gilbert , Matthew Dillon , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Wilko Bulte wrote: > On Thu, Dec 27, 2001 at 12:15:56AM +0100, Søren Schmidt wrote: > > It seems Matthew Gilbert wrote: > > > > So, general question to everyone having crashes during heavy > > > > IDE workloads: Please post your /var/run/dmesg.boot > > > > output. > > > > > atapci0: port 0xd000-0xd00f at device 7.1 on > > > > You have the VIA 82c686b southbridge chip which is known to cause severe > > Hi Soren, > > isn't it possible to identify the southbridge as a B variant directly? > > What I mean is, I have an older (non-B) > > isab0: at device 4.0 on pci0 > atapci0: port 0xd800-0xd80f at device 4.1 on > pci0 > pci0 > > and the strings that is displayed is almost the same (ATA100 versus > ATA66). > > Identifying it a bit more clearly might save a bunch of questions on > the lists. Well I think the ATA66 versus ATA100 is plenty different to tell which version we've dealing with here, and there's already new chipsets from VIA that uses the same ID's but with different chip names, so the chip number is more or less without meaning anyways.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 5: 9: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id C296737B41A; Thu, 27 Dec 2001 05:08:57 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBRD8nq18165; Thu, 27 Dec 2001 14:08:49 +0100 (CET) (envelope-from wkb) Date: Thu, 27 Dec 2001 14:08:49 +0100 From: Wilko Bulte To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: Matthew Gilbert , Matthew Dillon , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers Message-ID: <20011227140849.D17992@freebie.xs4all.nl> References: <20011227140303.C17992@freebie.xs4all.nl> <200112271307.fBRD7Ma47234@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200112271307.fBRD7Ma47234@freebsd.dk>; from sos@freebsd.dk on Thu, Dec 27, 2001 at 02:07:22PM +0100 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 27, 2001 at 02:07:22PM +0100, Søren Schmidt wrote: > It seems Wilko Bulte wrote: > > On Thu, Dec 27, 2001 at 12:15:56AM +0100, Søren Schmidt wrote: > > > It seems Matthew Gilbert wrote: > > > > > So, general question to everyone having crashes during heavy > > > > > IDE workloads: Please post your /var/run/dmesg.boot > > > > > output. > > > > > > > atapci0: port 0xd000-0xd00f at device 7.1 on > > > > > > You have the VIA 82c686b southbridge chip which is known to cause severe > > > > Hi Soren, > > > > isn't it possible to identify the southbridge as a B variant directly? > > > > What I mean is, I have an older (non-B) > > > > isab0: at device 4.0 on pci0 > > atapci0: port 0xd800-0xd80f at device 4.1 on > > pci0 > > pci0 > > > > and the strings that is displayed is almost the same (ATA100 versus > > ATA66). > > > > Identifying it a bit more clearly might save a bunch of questions on > > the lists. > > Well I think the ATA66 versus ATA100 is plenty different to tell > which version we've dealing with here, and there's already new > chipsets from VIA that uses the same ID's but with different Lovely idea.. not. > chip names, so the chip number is more or less without meaning > anyways.... Bah.. so much for my theory then :-( tnx Wilko -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 5:21:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (law2-f37.hotmail.com [216.32.181.37]) by hub.freebsd.org (Postfix) with ESMTP id 9B26437B405 for ; Thu, 27 Dec 2001 05:21:54 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 27 Dec 2001 05:21:54 -0800 Received: from 24.196.232.63 by lw2fd.hotmail.msn.com with HTTP; Thu, 27 Dec 2001 13:21:54 GMT X-Originating-IP: [24.196.232.63] From: "Kenneth Mays" To: ruben@verweg.com, freebsd-stable@FreeBSD.ORG Subject: Re: symmetric multiprocessing: MPS 1.4 recommended ? Date: Thu, 27 Dec 2001 08:21:54 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 27 Dec 2001 13:21:54.0506 (UTC) FILETIME=[73CEBAA0:01C18ED9] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks for the tip!!! Most of the time, the BIOS (firmware) is the conflict but we like to blame the OS or drivers. It is all relative. I suggest first checking the firmware, then the drivers, then the OS. Ken _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 5:49:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id CE51837B416; Thu, 27 Dec 2001 05:49:33 -0800 (PST) Received: from pfrench by mailhost.firstcallgroup.co.uk with local (Exim 3.33 #1) id 16JauV-000Mgg-00; Thu, 27 Dec 2001 13:49:27 +0000 To: sos@freebsd.dk Subject: Re: Need PCI/VIA chipset help (was Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <200112262141.fBQLfP319423@freebsd.dk> Message-Id: From: Pete French Date: Thu, 27 Dec 2001 13:49:27 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Anyhow since this is not always the case I did the fix for -current, > granted it should not be in the ATA driver, but since nobody else > really cared at the time.... Does this mean that if you dont have the ATA drivers in the kernel then you wont get the fix ? As the bug occurs under high PCI loads then this can potentially affect people with large amounts of PCI activity on SCSI drives too surely ? Granted I've never seen it happen, but it still bothers me that it might... -pcf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 6:15:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 1064D37B405; Thu, 27 Dec 2001 06:15:20 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id fBREFFl64118; Thu, 27 Dec 2001 15:15:15 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200112271415.fBREFFl64118@freebsd.dk> Subject: Re: Need PCI/VIA chipset help (was Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers) In-Reply-To: To: Pete French Date: Thu, 27 Dec 2001 15:15:15 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Pete French wrote: > > Anyhow since this is not always the case I did the fix for -current, > > granted it should not be in the ATA driver, but since nobody else > > really cared at the time.... > > Does this mean that if you dont have the ATA drivers in the kernel then > you wont get the fix ? As the bug occurs under high PCI loads then this > can potentially affect people with large amounts of PCI activity on > SCSI drives too surely ? Granted I've never seen it happen, but it still > bothers me that it might... As far as I'm able to tell, the problem can appear with any PCI device that can generate enough PCI traffic for the bug to appear, or at least my tests points in that direction. However I dont have any SCSI equipment here so I cant tell if that can trigger the problem... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 6:20:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from valen.gwi.net (valen.gwi.net [207.5.128.33]) by hub.freebsd.org (Postfix) with ESMTP id 50BA637B419; Thu, 27 Dec 2001 06:20:19 -0800 (PST) Received: from ABERRATION (dieselgeek.outofspec.com [207.5.188.11]) by valen.gwi.net (8.11.6/8.11.6) with SMTP id fBREKIJ21622; Thu, 27 Dec 2001 09:20:18 -0500 (EST) Message-ID: <005101c18ee1$9b5d66e0$fa01a8c0@ABERRATION> Reply-To: "Predius" From: "Predius" Cc: , References: Subject: Re: Need PCI/VIA chipset help (was Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers) Date: Thu, 27 Dec 2001 09:20:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There are a couple known issues going on with the VIA Chipset line (Some acknowledge by VIA partially, some not.) beyond just the 686B bug. Here's a couple sites with details. Myself, I think it's a BIOS writer's problem as well, but unfortunatly with most VIA boards, their goal is performance over stability, leaving people like us SOL. http://www.networking.tzo.com/net/software/ http://www.tecchannel.de/hardware/813/1.html <- In german, bring your fish Myself, I'd love to see a couple kernel options that could impliment the chipset tweaks, I think they'd most appropriately be included with the other cpu tweaks, and should have an appropriate warning attached to them. Joshua Coombs ----- Original Message ----- From: "Pete French" To: Cc: ; Sent: Thursday, December 27, 2001 8:49 AM Subject: Re: Need PCI/VIA chipset help (was Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers) > > Anyhow since this is not always the case I did the fix for -current, > > granted it should not be in the ATA driver, but since nobody else > > really cared at the time.... > > Does this mean that if you dont have the ATA drivers in the kernel then > you wont get the fix ? As the bug occurs under high PCI loads then this > can potentially affect people with large amounts of PCI activity on > SCSI drives too surely ? Granted I've never seen it happen, but it still > bothers me that it might... > > -pcf. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 6:32:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sofia.digsys.bg (sofia.digsys.bg [193.68.3.250]) by hub.freebsd.org (Postfix) with ESMTP id 6161C37B405 for ; Thu, 27 Dec 2001 06:32:52 -0800 (PST) Received: from comm.uni-svishtov.bg (ns.uni-svishtov.bg [193.68.172.1]) by sofia.digsys.bg (8.9.0/8.9.0) with ESMTP id QAA18647 for ; Thu, 27 Dec 2001 16:32:47 +0200 (EET) Received: from grinch.uni-svishtov.bg (root@grinch.uni-svishtov.bg [193.68.172.9]) by comm.uni-svishtov.bg (8.9.3/8.9.3) with ESMTP id QAA15834 for ; Thu, 27 Dec 2001 16:32:45 +0200 (EET) Received: from deckland (deckland.uni-svishtov.bg [193.68.173.82]) by grinch.uni-svishtov.bg (8.9.3/8.9.1) with SMTP id QAA28842 for ; Thu, 27 Dec 2001 16:32:44 +0200 (EET) Message-ID: <000801c18ee3$55e361d0$52ad44c1@deckland> From: "Radoslav Vasilev" To: Subject: Freebsd cvs repository size Date: Thu, 27 Dec 2001 16:32:38 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C18EF4.193B36C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C18EF4.193B36C0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable I'd like to know how large is the cvs repository for making cvsup-mirror = server on both stable and -current branches for the source-tree. thanks = in advance! ------=_NextPart_000_0005_01C18EF4.193B36C0 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
I'd like to know how large is the cvs = repository=20 for making cvsup-mirror server on both stable and -current branches for = the=20 source-tree. thanks in advance!
------=_NextPart_000_0005_01C18EF4.193B36C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 6:35:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 2FE6437B417; Thu, 27 Dec 2001 06:35:40 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id fBREZbm68994; Thu, 27 Dec 2001 15:35:37 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200112271435.fBREZbm68994@freebsd.dk> Subject: Re: Need PCI/VIA chipset help (was Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers) In-Reply-To: <200112271415.fBREFFl64118@freebsd.dk> To: sos@freebsd.dk Date: Thu, 27 Dec 2001 15:35:37 +0100 (CET) Cc: Pete French , freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Søren Schmidt wrote: > > Does this mean that if you dont have the ATA drivers in the kernel then > > you wont get the fix ? As the bug occurs under high PCI loads then this > > can potentially affect people with large amounts of PCI activity on > > SCSI drives too surely ? Granted I've never seen it happen, but it still > > bothers me that it might... > > As far as I'm able to tell, the problem can appear with any PCI device > that can generate enough PCI traffic for the bug to appear, or > at least my tests points in that direction. However I dont have > any SCSI equipment here so I cant tell if that can trigger the > problem... Hmm, just flipped through some of my notes on this, to be precise I can *not* say that any PCI device can cause this problem, all cases I have has the 686b device as part of the equation, so what we need to show is that there is a problem (or not) when not using the 686b part at all (ie no ATA channels, no VIA sound, no USB traffic and possbily more I've forgotten the 686b handles). If corruption can still appear the fix is "generic". Mind you the fix VIA originally brought out was just to cope with data corruption when using a SB live! and the onboard ATA channels simultaniously. Intensive testing then revealed that the problem could also appear without the SBlive! in the mix, but only banging on the ATA channels (a simple 'dd' between two fast disks one on each channel reveals the bug within seconds). I then did alot of testing using various means of generating lots of PCI traffic, but I can only say from the results I saved that the corruption appeared when the 686b was involved, I dont have any significant data that shows that high PCI loads without the 686b involved fails/works. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 7:27:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 5988E37B41A; Thu, 27 Dec 2001 07:27:35 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBRFRU418518; Thu, 27 Dec 2001 16:27:30 +0100 (CET) (envelope-from wkb) Date: Thu, 27 Dec 2001 16:27:30 +0100 From: Wilko Bulte To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: Pete French , freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Need PCI/VIA chipset help (was Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers) Message-ID: <20011227162730.B18482@freebie.xs4all.nl> References: <200112271415.fBREFFl64118@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200112271415.fBREFFl64118@freebsd.dk>; from sos@freebsd.dk on Thu, Dec 27, 2001 at 03:15:15PM +0100 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 27, 2001 at 03:15:15PM +0100, Søren Schmidt wrote: > It seems Pete French wrote: > > > Anyhow since this is not always the case I did the fix for -current, > > > granted it should not be in the ATA driver, but since nobody else > > > really cared at the time.... > > > > Does this mean that if you dont have the ATA drivers in the kernel then > > you wont get the fix ? As the bug occurs under high PCI loads then this > > can potentially affect people with large amounts of PCI activity on > > SCSI drives too surely ? Granted I've never seen it happen, but it still > > bothers me that it might... > > As far as I'm able to tell, the problem can appear with any PCI device > that can generate enough PCI traffic for the bug to appear, or > at least my tests points in that direction. However I dont have That would (I think) mean that say a Hauppauge TVcard would also be capable to trigger the problem. Esp. when one uses the fxtv capture to disk option. -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 7:33:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 1DBB237B41E; Thu, 27 Dec 2001 07:33:11 -0800 (PST) Received: from colt.ncptiddische.net (ppp-210.wobline.de [212.68.69.221]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fBRFX1830283; Thu, 27 Dec 2001 16:33:01 +0100 Received: from tisys.org (poison.ncptiddische.net [192.168.0.5]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fBRFWwX74861; Thu, 27 Dec 2001 16:32:59 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id fBRFWqO00187; Thu, 27 Dec 2001 16:32:52 +0100 (CET) (envelope-from nils) Date: Thu, 27 Dec 2001 16:32:52 +0100 From: Nils Holland To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: Matthew Dillon , Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers Message-ID: <20011227163252.A151@tisys.org> Mail-Followup-To: =?iso-8859-1?Q?S=F8ren_Schmidt?= , Matthew Dillon , Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <200112262355.fBQNtfK48250@apollo.backplane.com> <200112270945.fBR9j1e97273@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200112270945.fBR9j1e97273@freebsd.dk>; from sos@freebsd.dk on Thu, Dec 27, 2001 at 10:45:01AM +0100 X-Operating-System: FreeBSD poison.ncptiddische.net 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE X-Machine-Uptime: 4:24PM up 50 secs, 1 user, load averages: 0.07, 0.03, 0.01 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 27, 2001 at 10:45:01AM +0100, Søren Schmidt stood up and spoke: > > OK, here goes the VIA 686b patch, it is hand cut out from the bulk patches > to go into 4.5 so beware :) Well, as Matt has said, I reported a crash that he's trying to debug. Since I have the 686b in my machine, I applied the patch. Ever since then I was not able to reproduce the crash again, although yesterday it was so easy that I could do it twice an hour ;-) Anyway, you (Soren) said that the right way to fix this is a BIOS update. Now, could it be that some mainboard manufacturers are incapabel of handling this? I'm using the latest BIOS for my board, and according to http://www.chaintech.com.tw/DL/7xMB/7AJA0.HTM, this should already have been fixed in their BIOS release from 2001-04-23... Second interesting thing: I was using a UDMA66 drive on my 686b until a few weeks ago and never had any problems - the stuff Matt is looking at only started two appear a short while after I exchanged that drive for a UDMA100 one. So, it seems as if probably the slower drive didn't produce a high enough PCI workload for anything to actually happen. This fix will probably also have some influence on a few other similar problems (I read Matt was working on many of them). In the end I hope that this fix - or a variation thereof - will actually go into 4.5. Greetings Nils -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 7:55:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 1531D37B41A for ; Thu, 27 Dec 2001 07:55:44 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id fBRFthG09768; Thu, 27 Dec 2001 07:55:43 -0800 (PST) (envelope-from david) Date: Thu, 27 Dec 2001 07:55:43 -0800 (PST) From: David Wolfskill Message-Id: <200112271555.fBRFthG09768@bunrab.catwhisker.org> To: freebsd-stable@FreeBSD.ORG, rvasilev@uni-svishtov.bg Subject: Re: Freebsd cvs repository size In-Reply-To: <000801c18ee3$55e361d0$52ad44c1@deckland> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >From: "Radoslav Vasilev" >Date: Thu, 27 Dec 2001 16:32:38 +0200 >I'd like to know how large is the cvs repository for making cvsup-mirror = >server on both stable and -current branches for the source-tree. thanks = >in advance! This query was answered in the responses to http://docs.freebsd.org/cgi/getmsg.cgi?fetch=408650+0+archive/2001/freebsd-stable/20011125.freebsd-stable, from 21 November, 2001. But here are the results from the FreeBSD portions of 3 different repositories to which I have ready access: cvs[3]% sudo du -ks freebsd Password: 1377671 freebsd freebeast[3] sudo du -ks freebsd Password: 1372311 freebsd g1-7[3] sudo du -ks freebsd Password: 1372419 freebsd So, it looks like somewhat less than 1.5 GB. I suggest allowing for growth -- both from the FreeBSD portion of the repository, and for putting other data in the repository. Cheers, david -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 8:53:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id D807837B405 for ; Thu, 27 Dec 2001 08:53:49 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id fBRGrnd27968 for freebsd-stable@FreeBSD.ORG; Thu, 27 Dec 2001 08:53:49 -0800 Date: Thu, 27 Dec 2001 08:53:49 -0800 From: Brooks Davis To: freebsd-stable@FreeBSD.ORG Subject: Re: IT'S FIXED!! Whew! (was:Make Installworld fills up / ...help!) Message-ID: <20011227085348.A27331@Odin.AC.HMC.Edu> References: <3C22915C.F31E2C61@attbi.com> <20011220174037.A1142@Odin.AC.HMC.Edu> <3C2294FE.CB900677@attbi.com> <20011220180038.A3775@Odin.AC.HMC.Edu> <3C24B0B9.2597A8D9@attbi.com> <20011222162056.A28561@Odin.AC.HMC.Edu> <20011223002903.GB34036@laptop.lambertfam.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011223002903.GB34036@laptop.lambertfam.org>; from lambert@lambertfam.org on Sat, Dec 22, 2001 at 07:29:03PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 22, 2001 at 07:29:03PM -0500, Scott Lambert wrote: > On Sat, Dec 22, 2001 at 04:20:56PM -0800, Brooks Davis wrote: > > I wonder if we should consider adding a check to > > installworld/installkernel to refuse to install on very small / > > partitions since the failure mode is really ugly (losing files in /bin > > or /sbin). >=20 > I have a system with and extremely small / partition. I get around this= =20 > by sitting on another console entering "sync && sync && sync" every few= =20 > seconds. Would it be possible to check for a small / partition and if=20 > it is tight, kick off a small script that forces softupdates to flush > all pending updates every 30 seconds or so? This would seem to be=20 > better than just leaving the user out in the cold. This would only help people who a) ignored the advice to not do this and b) are not actually out of space. I can't really bring my self to care much about the problems of people who run softupdates on small /'s (though I suppose I'm concerned about the people on -questions and -stable who have to deal with them). I'm much more concerned about installs failing due to actually running out of space due to module growth. -- Brooks --=20 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 --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8K1IcXY6L6fI4GtQRAgyoAKC/vbB/3YBu1pmxtIc4z72vSAdVfgCggqB5 4R0mfhmf/PyfLNPRv+rM5Q8= =AHBo -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 9: 6:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sofia.digsys.bg (sofia.digsys.bg [193.68.3.250]) by hub.freebsd.org (Postfix) with ESMTP id B02FD37B417 for ; Thu, 27 Dec 2001 09:06:25 -0800 (PST) Received: from comm.uni-svishtov.bg (ns.uni-svishtov.bg [193.68.172.1]) by sofia.digsys.bg (8.9.0/8.9.0) with ESMTP id TAA06040 for ; Thu, 27 Dec 2001 19:06:18 +0200 (EET) Received: from grinch.uni-svishtov.bg (root@grinch.uni-svishtov.bg [193.68.172.9]) by comm.uni-svishtov.bg (8.9.3/8.9.3) with ESMTP id TAA23467 for ; Thu, 27 Dec 2001 19:06:16 +0200 (EET) Received: from deckland (deckland.uni-svishtov.bg [193.68.173.82]) by grinch.uni-svishtov.bg (8.9.3/8.9.1) with SMTP id TAA00603 for ; Thu, 27 Dec 2001 19:06:15 +0200 (EET) Message-ID: <001a01c18ef8$c8057900$0201a8c0@deckland> From: "Radoslav Vasilev" To: Subject: FreeBSD cvs repository size Date: Thu, 27 Dec 2001 19:06:09 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0017_01C18F09.8B41D6B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0017_01C18F09.8B41D6B0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable 10x for all the answers again. ------=_NextPart_000_0017_01C18F09.8B41D6B0 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
10x for all the answers=20 again.
------=_NextPart_000_0017_01C18F09.8B41D6B0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 9:25:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id A4A6D37B416 for ; Thu, 27 Dec 2001 09:25:22 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id fBRHPAj29352; Thu, 27 Dec 2001 09:25:10 -0800 Date: Thu, 27 Dec 2001 09:25:10 -0800 From: Brooks Davis To: Eugene Grosbein Cc: stable@FreeBSD.ORG Subject: Re: buggy gif in 4.4-STABLE (2 November 2001) Message-ID: <20011227092510.C27331@Odin.AC.HMC.Edu> References: <20011221143743.A68938@svzserv.kemerovo.su> <20011221111514.A30629@Odin.AC.HMC.Edu> <3C260C45.895B543C@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="DIOMP1UsTsWJauNi" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C260C45.895B543C@grosbein.pp.ru>; from eugen@grosbein.pp.ru on Sun, Dec 23, 2001 at 11:54:29PM +0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --DIOMP1UsTsWJauNi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 23, 2001 at 11:54:29PM +0700, Eugene Grosbein wrote: > Brooks Davis wrote: >=20 > > > 1. It is impossible to kldload if_gif.ko when kernel was compiled wit= hout IPv6. > >=20 > > If you're building a custom kernel you should compile in your devices. >=20 > This is what I generally do. But often it's impossible to predict > what will be nessesary later and it's undesirable to include all possible > features into production kernel :) > My kernel runs with securelevel=3D2 and integration of gif was a bit pain= ful. > Aren't kernel modules designed for similar situation? Absolutly not. You can't load modules at securelevel>0. The fact that the modules really only work with generic is a bug, but it's not going to be fixed in stable, so you'll just have to deal with it. -- Brooks --=20 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 --DIOMP1UsTsWJauNi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8K1l2XY6L6fI4GtQRAhC0AJ96T/P6uAHveUtNlmROKZEe3zld3QCdH2KC tYCNe/x2vzF4vPeWAVE8D+E= =dG2+ -----END PGP SIGNATURE----- --DIOMP1UsTsWJauNi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 9:39:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from viator.haloflightleader.net (adsl-63-197-56-193.dsl.lsan03.pacbell.net [63.197.56.193]) by hub.freebsd.org (Postfix) with ESMTP id 2EAAF37B41A for ; Thu, 27 Dec 2001 09:39:17 -0800 (PST) Received: from ongppla (hogan-and-hartson-llp.Washington.cw.net [208.173.12.150]) by viator.haloflightleader.net (8.11.6/8.11.6) with SMTP id fBRIUvp01620 for ; Thu, 27 Dec 2001 10:30:58 -0800 (PST) (envelope-from peter@haloflightleader.net) Message-ID: <004001c18efd$5627bf00$245b1486@hhlaw.com> From: "Peter/Los Angeles, CA" To: Subject: /usr/local/etc/rc.d/apache.sh question Date: Thu, 27 Dec 2001 09:38:40 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I have some understanding of how the script works, but I'm not sure what it's asking for. [09:37][root@interim:/usr/local/etc/rc.d]# ls apache.sh* [09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start ./apache.sh: Cannot determine the PREFIX That's what I get. The following will be the contents of apache.sh: #!/bin/sh if ! PREFIX=$(expr $0 : "\(/.*\)/etc/rc\.d/$(basename $0)\$"); then echo "$0: Cannot determine the PREFIX" >&2 exit 1 fi case "$1" in start) [ -x ${PREFIX}/sbin/apachectl ] && ${PREFIX}/sbin/apachectl start > /dev/null && echo -n ' apache' ;; stop) [ -r /var/run/httpd.pid ] && ${PREFIX}/sbin/apachectl stop > /dev/null && echo -n ' apache' ;; *) echo "Usage: `basename $0` {start|stop}" >&2 ;; esac exit 0 Can someone please help? If I type apachectl as I usually have done in Linux, it works, but now this is asking me for something. Can someone please help? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 9:43:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bunning.skiltech.com (bunning.skiltech.com [216.235.79.240]) by hub.freebsd.org (Postfix) with ESMTP id 7021637B417 for ; Thu, 27 Dec 2001 09:43:45 -0800 (PST) Received: (from root@localhost) by bunning.skiltech.com (8.11.6/8.11.6) id fBRHhi550258; Thu, 27 Dec 2001 12:43:44 -0500 (EST) (envelope-from minter) Received: (from minter@localhost) by bunning.skiltech.com (8.11.6/8.11.6) id fBRHhhR50250; Thu, 27 Dec 2001 12:43:43 -0500 (EST) (envelope-from minter) Date: Thu, 27 Dec 2001 12:43:43 -0500 (EST) From: "H. Wade Minter" X-X-Sender: minter@bunning.skiltech.com To: "Peter/Los Angeles, CA" Cc: freebsd-stable@freebsd.org Subject: Re: /usr/local/etc/rc.d/apache.sh question In-Reply-To: <004001c18efd$5627bf00$245b1486@hhlaw.com> Message-ID: <20011227124303.P50221-100000@bunning.skiltech.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 27 Dec 2001, Peter/Los Angeles, CA wrote: > I have some understanding of how the script works, but I'm not sure what > it's asking for. > > [09:37][root@interim:/usr/local/etc/rc.d]# ls > apache.sh* > [09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start > ./apache.sh: Cannot determine the PREFIX > > That's what I get. The following will be the contents of apache.sh: It determines the PREFIX by the full path you use to call the script. If you run: /usr/local/etc/rc.d/apache.sh start it will work. --Wade To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 9:44:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by hub.freebsd.org (Postfix) with ESMTP id EABCB37B416 for ; Thu, 27 Dec 2001 09:44:08 -0800 (PST) Received: by freebsd.org.ru (Postfix, from userid 1000) id 82860251; Thu, 27 Dec 2001 20:44:06 +0300 (MSK) Date: Thu, 27 Dec 2001 20:44:06 +0300 From: "Sergey A. Osokin" To: "Peter/Los Angeles, CA" Cc: stable@FreeBSD.org Subject: Re: /usr/local/etc/rc.d/apache.sh question Message-ID: <20011227204406.A40396@freebsd.org.ru> Reply-To: osa@freebsd.org.ru References: <004001c18efd$5627bf00$245b1486@hhlaw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004001c18efd$5627bf00$245b1486@hhlaw.com>; from peter@haloflightleader.net on Thu, Dec 27, 2001 at 09:38:40AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 27, 2001 at 09:38:40AM -0800, Peter/Los Angeles, CA wrote: > Hello, > > I have some understanding of how the script works, but I'm not sure what > it's asking for. > > [09:37][root@interim:/usr/local/etc/rc.d]# ls > apache.sh* > [09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start > ./apache.sh: Cannot determine the PREFIX Looks like you must use full path for this shell-script. Like this: [09:37][root@interim:/usr/local/etc/rc.d]# /usr/local/etc/rc.d/apache.sh start -- Rgdz, /"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN osa@freebsd.org.ru X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 9:44:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.mediadesign.nl (md2.mediadesign.nl [212.19.205.67]) by hub.freebsd.org (Postfix) with SMTP id 90F4C37B405 for ; Thu, 27 Dec 2001 09:44:32 -0800 (PST) Received: (qmail 12991 invoked by uid 1002); 27 Dec 2001 17:44:25 -0000 From: "Alson van der Meulen" Date: Thu, 27 Dec 2001 18:44:25 +0100 To: freebsd-stable@FreeBSD.ORG Subject: Re: /usr/local/etc/rc.d/apache.sh question Message-ID: <20011227184425.F11901@alm.xs4all.nl> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <004001c18efd$5627bf00$245b1486@hhlaw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004001c18efd$5627bf00$245b1486@hhlaw.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter/Los Angeles, CA(peter@haloflightleader.net)@2001.12.27 09:38:40 +0000: > Hello, > > I have some understanding of how the script works, but I'm not sure what > it's asking for. > > [09:37][root@interim:/usr/local/etc/rc.d]# ls > apache.sh* > [09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start > ./apache.sh: Cannot determine the PREFIX try /usr/local/etc/rc.d/apache.sh start To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 9:47: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from viator.haloflightleader.net (adsl-63-197-56-193.dsl.lsan03.pacbell.net [63.197.56.193]) by hub.freebsd.org (Postfix) with ESMTP id A5E5637B405 for ; Thu, 27 Dec 2001 09:47:02 -0800 (PST) Received: from ongppla (hogan-and-hartson-llp.Washington.cw.net [208.173.12.150]) by viator.haloflightleader.net (8.11.6/8.11.6) with SMTP id fBRIcXp01671; Thu, 27 Dec 2001 10:38:34 -0800 (PST) (envelope-from peter@haloflightleader.net) Message-ID: <006701c18efe$66b28f20$245b1486@hhlaw.com> From: "Peter/Los Angeles, CA" To: "H. Wade Minter" Cc: References: <20011227124303.P50221-100000@bunning.skiltech.com> Subject: Re: /usr/local/etc/rc.d/apache.sh question Date: Thu, 27 Dec 2001 09:46:16 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You guys are great. Thanks a lot. I owe you guys my first born. Peter ----- Original Message ----- From: "H. Wade Minter" To: "Peter/Los Angeles, CA" Cc: Sent: Thursday, December 27, 2001 9:43 AM Subject: Re: /usr/local/etc/rc.d/apache.sh question > On Thu, 27 Dec 2001, Peter/Los Angeles, CA wrote: > > > I have some understanding of how the script works, but I'm not sure what > > it's asking for. > > > > [09:37][root@interim:/usr/local/etc/rc.d]# ls > > apache.sh* > > [09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start > > ./apache.sh: Cannot determine the PREFIX > > > > That's what I get. The following will be the contents of apache.sh: > > It determines the PREFIX by the full path you use to call the script. If > you run: > > /usr/local/etc/rc.d/apache.sh start > > it will work. > > --Wade > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 9:53:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from viator.haloflightleader.net (adsl-63-197-56-193.dsl.lsan03.pacbell.net [63.197.56.193]) by hub.freebsd.org (Postfix) with ESMTP id 117E637B419 for ; Thu, 27 Dec 2001 09:53:32 -0800 (PST) Received: from ongppla (hogan-and-hartson-llp.Washington.cw.net [208.173.12.150]) by viator.haloflightleader.net (8.11.6/8.11.6) with SMTP id fBRIjCp01691 for ; Thu, 27 Dec 2001 10:45:12 -0800 (PST) (envelope-from peter@haloflightleader.net) Message-ID: <007801c18eff$53b107c0$245b1486@hhlaw.com> From: "Peter/Los Angeles, CA" To: Subject: apache question part2 Date: Thu, 27 Dec 2001 09:52:54 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear People, Thank you for your help with my initial apache question. I don't know if this is a malfunction or what, although it seems to work. I opened up the router, and directed it to my server at home. It's responding so I know the daemon is working. The number of times that I've used apache, I've never seen this as an initial message. Is it possible that it's just the port that had some corrupted initial message? Anyway, I'll try the other pages in that directory. Take a look at what I'm talking about. http://haloflightleader.net Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10: 7:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 0619137B419 for ; Thu, 27 Dec 2001 10:07:09 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA06612; Thu, 27 Dec 2001 11:05:40 -0700 (MST) (envelope-from chad) Date: Thu, 27 Dec 2001 11:05:40 -0700 From: "Chad R. Larson" To: "Igor I. Ushatinsky" Cc: Vladimir Perepechenko , stable@FreeBSD.ORG Subject: Re: Where can I get (download) Free BSD 2.2.7 Release ? Message-ID: <20011227110540.A6362@freeway.dcfinc.com> References: <20011015231530.A21091@freeway.dcfinc.com> <1833336487.20011227123831@adm.msi.ru> <3C2AA60B.4070607@tng.tmn.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C2AA60B.4070607@tng.tmn.ru>; from igor@tng.tmn.ru on Thu, Dec 27, 2001 at 09:39:39AM +0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 27, 2001 at 09:39:39AM +0500, Igor I. Ushatinsky wrote: > Hi, Vladimir! >> I couldn/t find it at ftp://ftp.freebsd.org > > You may find 2.1.7.1-RELEASE at > ftp://ftp4.ru.freebsd.org/pub/FreeBSD/releases/i386/ I have the CD set for 2.1.7 and 2.2.8. If you can't find it elsewhere, I could probably put them up somewhere accessable. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:13:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id EBB5937B417 for ; Thu, 27 Dec 2001 10:13:51 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA06645; Thu, 27 Dec 2001 11:13:47 -0700 (MST) (envelope-from chad) Date: Thu, 27 Dec 2001 11:13:47 -0700 From: "Chad R. Larson" To: "Philip J. Koenig" Cc: stable@FreeBSD.ORG, William Carrel Subject: Re: 4.5 PRERELEASE - Call for testing Message-ID: <20011227111347.B6362@freeway.dcfinc.com> References: <3C2A1786.17075.63462D@localhost> <3C2A416C.12065.106F4F3@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C2A416C.12065.106F4F3@localhost>; from pjklist@ekahuna.com on Wed, Dec 26, 2001 at 09:30:20PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 26, 2001 at 09:30:20PM -0800, Philip J. Koenig wrote: > On 26 Dec 2001, at 19:56, William Carrel boldly uttered: >> Using switch settings to obtain this sort of configuration/protection is >> at best crude. Try dummynet(4) and/or some QoS capable network >> hardware. > > The switches and NICs for many years already should have the inherent > ability to run locked at 10Mbps. Indeed they push this as a > "feature". Why should I go spend outrageous sums on overpriced "QoS" > hardware or install an entirely new box for this purpose when the > existing switches and NICs should already do what I need? I too support hierarchical bandwidth topologies. Unless you're banging around medical images or such, 10Mbps to the desktop is plenty. Then connect the switches/hubs together at 100Mbps, and use gigabit between any core routers. That way, no one user can saturate a segment. Happier users, happier me. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:16: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from viator.haloflightleader.net (adsl-63-197-56-193.dsl.lsan03.pacbell.net [63.197.56.193]) by hub.freebsd.org (Postfix) with ESMTP id 9E5DA37B41A for ; Thu, 27 Dec 2001 10:15:52 -0800 (PST) Received: from ongppla (hogan-and-hartson-llp.Washington.cw.net [208.173.12.150]) by viator.haloflightleader.net (8.11.6/8.11.6) with SMTP id fBRJ7Pp01780; Thu, 27 Dec 2001 11:07:25 -0800 (PST) (envelope-from peter@haloflightleader.net) Message-ID: <00a701c18f02$6e712560$245b1486@hhlaw.com> From: "Peter/Los Angeles, CA" To: "Josh Tolbert" Cc: References: Subject: Re: /usr/local/etc/rc.d/apache.sh question Date: Thu, 27 Dec 2001 10:15:07 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks. ----- Original Message ----- From: "Josh Tolbert" To: "Peter/Los Angeles, CA" Cc: Sent: Thursday, December 27, 2001 10:05 AM Subject: Re: /usr/local/etc/rc.d/apache.sh question > Peter, > Take a look at what the script is doing. It's checking to see if > execution was started with a full path (/usr/local/etc/rc.d/apache.sh) > instead of a relative path (./apache.sh). > When you run apachectl (startssl, I suspect), apachectl asks for > whatever passphrase you used to encrypt the SSL key. > > Good luck, > Josh > > On Thu, 27 Dec 2001, Peter/Los Angeles, CA wrote: > > > Hello, > > > > I have some understanding of how the script works, but I'm not sure what > > it's asking for. > > > > [09:37][root@interim:/usr/local/etc/rc.d]# ls > > apache.sh* > > [09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start > > ./apache.sh: Cannot determine the PREFIX > > > > That's what I get. The following will be the contents of apache.sh: > > > > #!/bin/sh > > > > if ! PREFIX=$(expr $0 : "\(/.*\)/etc/rc\.d/$(basename $0)\$"); then > > echo "$0: Cannot determine the PREFIX" >&2 > > exit 1 > > fi > > > > case "$1" in > > start) > > [ -x ${PREFIX}/sbin/apachectl ] && ${PREFIX}/sbin/apachectl start > > > /dev/null && echo -n ' apache' > > ;; > > stop) > > [ -r /var/run/httpd.pid ] && ${PREFIX}/sbin/apachectl stop > > > /dev/null && echo -n ' apache' > > ;; > > *) > > echo "Usage: `basename $0` {start|stop}" >&2 > > ;; > > esac > > > > exit 0 > > > > Can someone please help? If I type apachectl as I usually have done in > > Linux, it works, but now this is asking me for something. Can someone > > please help? > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:26:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tenchi.dreamlabs.com (tenchi.dreamlabs.com [216.220.37.61]) by hub.freebsd.org (Postfix) with ESMTP id 77F0637B41A for ; Thu, 27 Dec 2001 10:26:33 -0800 (PST) Received: (from root@localhost) by tenchi.dreamlabs.com (8.11.6/8.11.6) id fBRIQWY60059; Thu, 27 Dec 2001 13:26:32 -0500 (EST) (envelope-from mitayai@dreamlabs.com) Received: from cr411661a (shadow.dreamlabs.com [216.129.214.38]) (authenticated) by tenchi.dreamlabs.com (8.11.6/8.11.6) with ESMTP id fBRIQJV60036; Thu, 27 Dec 2001 13:26:19 -0500 (EST) (envelope-from mitayai@dreamlabs.com) Reply-To: From: "Mit Rowe" To: "Peter/Los Angeles, CA" , Subject: RE: apache question part2 Date: Thu, 27 Dec 2001 13:25:47 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <007801c18eff$53b107c0$245b1486@hhlaw.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG turn off Multiviews in /usr/local/etc/apache/httpd.conf ;-) > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Peter/Los Angeles, > CA > Sent: December 27, 2001 12:53 > To: stable@FreeBSD.ORG > Subject: apache question part2 > > > Dear People, > > Thank you for your help with my initial apache question. I don't know if > this is a malfunction or what, although it seems to work. > > I opened up the router, and directed it to my server at home. It's > responding so I know the daemon is working. The number of times that I've > used apache, I've never seen this as an initial message. Is it possible > that it's just the port that had some corrupted initial message? Anyway, > I'll try the other pages in that directory. > > Take a look at what I'm talking about. > http://haloflightleader.net > Peter > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:30:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tenchi.dreamlabs.com (tenchi.dreamlabs.com [216.220.37.61]) by hub.freebsd.org (Postfix) with ESMTP id 84E0137B41B for ; Thu, 27 Dec 2001 10:30:41 -0800 (PST) Received: (from root@localhost) by tenchi.dreamlabs.com (8.11.6/8.11.6) id fBRIUfR60565; Thu, 27 Dec 2001 13:30:41 -0500 (EST) (envelope-from mitayai@dreamlabs.com) Received: from cr411661a (shadow.dreamlabs.com [216.129.214.38]) (authenticated) by tenchi.dreamlabs.com (8.11.6/8.11.6) with ESMTP id fBRIUYV60546; Thu, 27 Dec 2001 13:30:34 -0500 (EST) (envelope-from mitayai@dreamlabs.com) Reply-To: From: "Mit Rowe" To: , "Peter/Los Angeles, CA" , Subject: RE: apache question part2 Date: Thu, 27 Dec 2001 13:30:02 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sorry, i should have been more specific... there is at least one line (maybe more) in the apache config file that says... Options ... Multiviews .... remove the multiviews part, leaving the rest, and run apachectl restart > -----Original Message----- > From: Mit Rowe [mailto:mitayai@dreamlabs.com] > Sent: December 27, 2001 13:26 > To: Peter/Los Angeles, CA; stable@FreeBSD.ORG > Subject: RE: apache question part2 > > > turn off Multiviews in /usr/local/etc/apache/httpd.conf > > ;-) > > > > -----Original Message----- > > From: owner-freebsd-stable@FreeBSD.ORG > > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Peter/Los Angeles, > > CA > > Sent: December 27, 2001 12:53 > > To: stable@FreeBSD.ORG > > Subject: apache question part2 > > > > > > Dear People, > > > > Thank you for your help with my initial apache question. I > don't know if > > this is a malfunction or what, although it seems to work. > > > > I opened up the router, and directed it to my server at home. It's > > responding so I know the daemon is working. The number of > times that I've > > used apache, I've never seen this as an initial message. Is it possible > > that it's just the port that had some corrupted initial > message? Anyway, > > I'll try the other pages in that directory. > > > > Take a look at what I'm talking about. > > http://haloflightleader.net > > Peter > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:40:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from krusty.e-technik.uni-dortmund.de (krusty.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by hub.freebsd.org (Postfix) with ESMTP id A6E0A37B419 for ; Thu, 27 Dec 2001 10:40:36 -0800 (PST) Received: from emma1.emma.line.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1]) by krusty.e-technik.uni-dortmund.de (Postfix) with ESMTP id 876D3A3826 for ; Thu, 27 Dec 2001 19:40:34 +0100 (CET) Received: by emma1.emma.line.org (Postfix, from userid 500) id 96BF3A2003; Thu, 27 Dec 2001 19:40:31 +0100 (CET) To: freebsd-stable@freebsd.org Subject: tcpd not installed on 4.5-PRERELEASE From: Matthias Andree Date: 27 Dec 2001 19:40:31 +0100 Message-ID: Lines: 13 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I just cleandir'ed out my whole /usr/obj/src and rebuilt the world (4.5-PRERELEASE), installed it, and figured that tcpd seems to be missing from the install, while tcpdchk and tcpdmatch are installed. What's up here? Did I do something wrong? Is this worth a send-pr? Or is tcpd just not part of the system? -- Matthias Andree "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:41:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vortex.wa4phy.net (cc449817-a.mrtnz1.ga.home.com [24.12.79.51]) by hub.freebsd.org (Postfix) with ESMTP id 93F5D37B422 for ; Thu, 27 Dec 2001 10:41:03 -0800 (PST) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.11.6/8.11.6) with ESMTP id fBRIev154905 for ; Thu, 27 Dec 2001 13:40:57 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3C2B6B39.1BF124A6@vortex.wa4phy.net> Date: Thu, 27 Dec 2001 13:40:57 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-PRERELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Gnome Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Probably not the right place to ask, but am trying to start upgrading my ports junque. Gnome bombs out in the controlcenter... I assume there is a sequence to doing the build of gnome, but "core" and "build" both bomb out when trying to build controlcenter. Problem appears to be structure related, with a missing member. Can anybody provide any clues? Thanks.. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:48:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2B10B37B417; Thu, 27 Dec 2001 10:48:01 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBRIlxh52129; Thu, 27 Dec 2001 10:47:59 -0800 (PST) (envelope-from dillon) Date: Thu, 27 Dec 2001 10:47:59 -0800 (PST) From: Matthew Dillon Message-Id: <200112271847.fBRIlxh52129@apollo.backplane.com> To: Nils Holland Cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= , Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers References: <200112262355.fBQNtfK48250@apollo.backplane.com> <200112270945.fBR9j1e97273@freebsd.dk> <20011227163252.A151@tisys.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is great news! I'm crossing my fingers and hoping that Nils can't reproduce the crash any more with Soren's fix. Just to let you all know, Nils has been working his ass off helping me track his crash down. I've been pulling my hair out... I gave him patch after patch to test various conditions & panic if the nfs_node's hash list somehow got broken, and for the last week not a single one of those tests detected the problem prior to the panic. The nfs_node's hash list was being corrupted seemingly out of nowhere. The last two days I've had Nils use hardware watchpoints in DDB> to try to track down what was modifying the memory location, with no success. The watchpoint was catching the (correct) write to the list head but then failed to catch the corrupted write prior to the system panicing, which is what makes me believe it is some sort of chipset issue. Another thing to note: One of the really weird things about Nils crashes is that the same memory location was getting corrupted every time, five times in a row (which made it possible to use a hardware watch point). The corruption changed somewhat when he added the hardware watch point. Another similar set of crashes in the vm_page_list (that other people report, including a number of machines at Yahoo), have a similar M.O.... IDE drive, medium/heavy activity, but while corrupted address always winds up in the (static) vm_page array, it always tends to be slightly different. I'm hoping that it winds up being the same or similar issue. I'm not ruling out the possibility that chipsets other then the 686B have problems too. In anycase, Nils description makes a lot of sense. I've asked him to continue testing his system to make sure that this particular crash cannot be reproduced, and I am crossing my fingers. I'm also wondering how applicable this patch might be in regards to forcing a 'safe' mode for other PCI chipsets, to allow us to test it on non-686B machines that have similar problems. -Matt Matthew Dillon :On Thu, Dec 27, 2001 at 10:45:01AM +0100, Søren Schmidt stood up and spoke: :> :> OK, here goes the VIA 686b patch, it is hand cut out from the bulk patches :> to go into 4.5 so beware :) : :Well, as Matt has said, I reported a crash that he's trying to debug. Since :I have the 686b in my machine, I applied the patch. Ever since then I was :not able to reproduce the crash again, although yesterday it was so easy :that I could do it twice an hour ;-) : :Anyway, you (Soren) said that the right way to fix this is a BIOS update. :Now, could it be that some mainboard manufacturers are incapabel of :handling this? I'm using the latest BIOS for my board, and according to :http://www.chaintech.com.tw/DL/7xMB/7AJA0.HTM, this should already have :been fixed in their BIOS release from 2001-04-23... : :Second interesting thing: I was using a UDMA66 drive on my 686b until a few :weeks ago and never had any problems - the stuff Matt is looking at only :started two appear a short while after I exchanged that drive for a UDMA100 :one. So, it seems as if probably the slower drive didn't produce a high :enough PCI workload for anything to actually happen. : :This fix will probably also have some influence on a few other similar :problems (I read Matt was working on many of them). In the end I hope that :this fix - or a variation thereof - will actually go into 4.5. : :Greetings :Nils : :-- :Nils Holland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:49:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 27B2637B41B for ; Thu, 27 Dec 2001 10:49:39 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id KAA25253; Thu, 27 Dec 2001 10:49:26 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda25249; Thu Dec 27 10:49:10 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.6/8.9.1) id fBRIn4n63898; Thu, 27 Dec 2001 10:49:04 -0800 (PST) Received: from UNKNOWN(10.1.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdW63896; Thu Dec 27 10:48:56 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.6/8.9.1) id fBRImuO34602; Thu, 27 Dec 2001 10:48:56 -0800 (PST) Message-Id: <200112271848.fBRImuO34602@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpde34593; Thu Dec 27 10:48:02 2001 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Matthias Andree Cc: freebsd-stable@FreeBSD.ORG Subject: Re: tcpd not installed on 4.5-PRERELEASE In-reply-to: Your message of "27 Dec 2001 19:40:31 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Dec 2001 10:48:02 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Matthias Andree writes: > Hello, > > I just cleandir'ed out my whole /usr/obj/src and rebuilt the world > (4.5-PRERELEASE), installed it, and figured that tcpd seems to be > missing from the install, while tcpdchk and tcpdmatch are > installed. What's up here? Did I do something wrong? Is this worth a > send-pr? Or is tcpd just not part of the system? Tcpd is redundant under FreeBSD. FreeBSD's inetd uses libwrap (TCP/Wrapper library), effectively wrapping as if tcpd was in use. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD Ministry of Management Services Province of BC FreeBSD UNIX: cy@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:52:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.tekrealm.net (dsl081-247-162.sfo1.dsl.speakeasy.net [64.81.247.162]) by hub.freebsd.org (Postfix) with ESMTP id CD39D37B41B for ; Thu, 27 Dec 2001 10:52:20 -0800 (PST) Received: (from root@localhost) by freebsd.tekrealm.net (8.11.6/8.11.4) id fBRIqKF30863 for freebsd-stable@freebsd.org; Thu, 27 Dec 2001 10:52:20 -0800 (PST) (envelope-from elitetek@tekrealm.net) Received: (from elitetek@localhost) by freebsd.tekrealm.net (8.11.6/8.11.4av) id fBRIqJP30851 for freebsd-stable@freebsd.org; Thu, 27 Dec 2001 10:52:19 -0800 (PST) (envelope-from elitetek@tekrealm.net) X-Authentication-Warning: freebsd.tekrealm.net: elitetek set sender to elitetek@tekrealm.net using -f Date: Thu, 27 Dec 2001 10:52:19 -0800 From: Andrew Stuart To: freebsd-stable@freebsd.org Subject: Via 686B southbrige corruption.. Message-ID: <20011227105219.A30619@freebsd.tekrealm.net> Reply-To: elitetek@tekrealm.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG i dont have a via686b chipset.. but am having simular issues.. i can repeatedly panic the system by transfering large amounts of files from a pci adaptec 29160 to a ide harddrive, and also ide to ide harddrive.. pcib2: at device 1.0 on pci0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ahc0: port 0xdc00-0xdcff mem 0xe310a000-0xe310afff irq 5 at device 18.0 on pci0 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs ad0: 39082MB [79406/16/63] at ata0-master UDMA66 da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) i have also tested going from scsi to scsi and dont seem to have the issue. this is on known good hardware. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:55:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 733CF37B419 for ; Thu, 27 Dec 2001 10:55:37 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id KAA25321; Thu, 27 Dec 2001 10:55:26 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda25317; Thu Dec 27 10:55:21 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.6/8.9.1) id fBRItGS64022; Thu, 27 Dec 2001 10:55:16 -0800 (PST) Received: from UNKNOWN(10.1.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdJ63999; Thu Dec 27 10:54:57 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.6/8.9.1) id fBRIsv534651; Thu, 27 Dec 2001 10:54:57 -0800 (PST) Message-Id: <200112271854.fBRIsv534651@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdx34641; Thu Dec 27 10:54:42 2001 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Sam Drinkard Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Gnome In-reply-to: Your message of "Thu, 27 Dec 2001 13:40:57 EST." <3C2B6B39.1BF124A6@vortex.wa4phy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Dec 2001 10:54:42 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3C2B6B39.1BF124A6@vortex.wa4phy.net>, Sam Drinkard writes: > Probably not the right place to ask, but am trying to start upgrading my > ports junque. Gnome bombs out in the controlcenter... I assume there is > a sequence to doing the build of gnome, but "core" and "build" both > bomb out when trying to build controlcenter. Problem appears to be > structure related, with a missing member. > > Can anybody provide any clues? It's been my experience when upgrading Gnome, all of the Gnome ports and most of the bits and pieces that Gnome relies upon to build, e.g. bonobo, ORBit, glib, gtk, etc., need to be current. I've had the best results deinstalling all of Gnome and the bits and pieces it relies on then installing the gnome meta-port, allowing it to drag in whatever it depends upon. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD Ministry of Management Services Province of BC FreeBSD UNIX: cy@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 10:58:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 60D4637B41B for ; Thu, 27 Dec 2001 10:58:14 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBRIw8622630; Thu, 27 Dec 2001 19:58:08 +0100 (CET) (envelope-from wkb) Date: Thu, 27 Dec 2001 19:58:08 +0100 From: Wilko Bulte To: Andrew Stuart Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Via 686B southbrige corruption.. Message-ID: <20011227195808.D22493@freebie.xs4all.nl> References: <20011227105219.A30619@freebsd.tekrealm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011227105219.A30619@freebsd.tekrealm.net>; from elitetek@tekrealm.net on Thu, Dec 27, 2001 at 10:52:19AM -0800 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 27, 2001 at 10:52:19AM -0800, Andrew Stuart wrote: > i dont have a via686b chipset.. but am having simular issues.. > i can repeatedly panic the system by transfering large amounts > of files from a pci adaptec 29160 to a ide harddrive, and also > ide to ide harddrive.. Some time ago I could reliably panic my -stable box using a Hauppauge Bt878 based TV card and a 29160 SCSI board. I switched to a 2940 and things are now stable. Might be interesting for you to try another model Adaptec (if you have one of course). I saw this on both an Abit and an Asus slot-A Athlon board. Both with VIA chipsets (686, not a 686b) W/ -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 11: 1:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.tekrealm.net (dsl081-247-162.sfo1.dsl.speakeasy.net [64.81.247.162]) by hub.freebsd.org (Postfix) with ESMTP id 146AC37B41A for ; Thu, 27 Dec 2001 11:01:25 -0800 (PST) Received: (from root@localhost) by freebsd.tekrealm.net (8.11.6/8.11.4) id fBRJ1O131173; Thu, 27 Dec 2001 11:01:24 -0800 (PST) (envelope-from elitetek@tekrealm.net) Received: (from elitetek@localhost) by freebsd.tekrealm.net (8.11.6/8.11.4av) id fBRJ1NY31165; Thu, 27 Dec 2001 11:01:23 -0800 (PST) (envelope-from elitetek@tekrealm.net) X-Authentication-Warning: freebsd.tekrealm.net: elitetek set sender to elitetek@tekrealm.net using -f Date: Thu, 27 Dec 2001 11:01:23 -0800 From: Andrew Stuart To: Wilko Bulte Cc: freebsd-stable@freebsd.org Subject: Re: Via 686B southbrige corruption.. Message-ID: <20011227110123.A31057@freebsd.tekrealm.net> Reply-To: elitetek@tekrealm.net References: <20011227105219.A30619@freebsd.tekrealm.net> <20011227195808.D22493@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011227195808.D22493@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Thu, Dec 27, 2001 at 07:58:08PM +0100 X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 27 Dec 2001 at 19:58:08 +0100, Wilko Bulte wrote: > On Thu, Dec 27, 2001 at 10:52:19AM -0800, Andrew Stuart wrote: > > i dont have a via686b chipset.. but am having simular issues.. > > i can repeatedly panic the system by transfering large amounts > > of files from a pci adaptec 29160 to a ide harddrive, and also > > ide to ide harddrive.. > > Some time ago I could reliably panic my -stable box using a > Hauppauge Bt878 based TV card and a 29160 SCSI board. > I switched to a 2940 and things are now stable. Might be interesting > for you to try another model Adaptec (if you have one of course). > I saw this on both an Abit and an Asus slot-A Athlon board. Both > with VIA chipsets (686, not a 686b) > > W/ > actually i had an adaptec 2940 and also a 2940UW in the system prior to going to the 29160.. but thanks, thats useful info for a friends machine that has a hauppauge card and 29160 in it that seems to crash off and on. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 11:10:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shumai.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id 5C68437B417 for ; Thu, 27 Dec 2001 11:10:21 -0800 (PST) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.6/8.11.6) with ESMTP id fBRJAXa13093; Thu, 27 Dec 2001 14:10:34 -0500 (EST) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Thu, 27 Dec 2001 14:10:33 -0500 (EST) From: Joe Clarke To: Sam Drinkard Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Gnome In-Reply-To: <3C2B6B39.1BF124A6@vortex.wa4phy.net> Message-ID: <20011227140812.P11529-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 27 Dec 2001, Sam Drinkard wrote: > Probably not the right place to ask, but am trying to start upgrading my > ports junque. Gnome bombs out in the controlcenter... I assume there is > a sequence to doing the build of gnome, but "core" and "build" both > bomb out when trying to build controlcenter. Problem appears to be > structure related, with a missing member. > > Can anybody provide any clues? Maybe if you send the output of the build. Of course, this would be best continued on freebsd-gnome. One thing I might also suggest is to do: pkg_delete -r ORBit- e.g. pkg_delete -r ORBit-0.5.10 (whatever version of ORBit you have installed), then: cd /usr/ports/x11/gnome make all install In the future, portupgrade _should_ work with Gnome, but sometimes certain pieces (like ORBit) change, and require you to rebuild all of Gnome :-(. Joe > > Thanks.. > > Sam > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 11:31:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from krusty.e-technik.uni-dortmund.de (krusty.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by hub.freebsd.org (Postfix) with ESMTP id E164437B417 for ; Thu, 27 Dec 2001 11:30:54 -0800 (PST) Received: from emma1.emma.line.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1]) by krusty.e-technik.uni-dortmund.de (Postfix) with ESMTP id 1CC1CA3826 for ; Thu, 27 Dec 2001 20:30:53 +0100 (CET) Received: by emma1.emma.line.org (Postfix, from userid 500) id 3A9D0A2003; Thu, 27 Dec 2001 20:30:50 +0100 (CET) To: freebsd-stable@freebsd.org Subject: Re: tcpd not installed on 4.5-PRERELEASE References: <200112271848.fBRImuO34602@cwsys.cwsent.com> In-Reply-To: <200112271848.fBRImuO34602@cwsys.cwsent.com> From: Matthias Andree Date: 27 Dec 2001 20:30:49 +0100 Message-ID: Lines: 26 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group writes: > In message , Matthias Andree writes: > > Hello, > > > > I just cleandir'ed out my whole /usr/obj/src and rebuilt the world > > (4.5-PRERELEASE), installed it, and figured that tcpd seems to be > > missing from the install, while tcpdchk and tcpdmatch are > > installed. What's up here? Did I do something wrong? Is this worth a > > send-pr? Or is tcpd just not part of the system? > > Tcpd is redundant under FreeBSD. FreeBSD's inetd uses libwrap > (TCP/Wrapper library), effectively wrapping as if tcpd was in use. No, it is not redundant. I might have a different super-server than FreeBSD's inetd (tcpserver from DJB's ucspi-tcp!), or I might want to run a service without libwrap for efficiency reasons -- in that case, I'd have to run tcpd explicitly for the other services. -- Matthias Andree "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 11:37:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id CD82237B416; Thu, 27 Dec 2001 11:37:05 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id fBRJalu43412; Thu, 27 Dec 2001 20:36:47 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200112271936.fBRJalu43412@freebsd.dk> Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers In-Reply-To: <200112271847.fBRIlxh52129@apollo.backplane.com> To: Matthew Dillon Date: Thu, 27 Dec 2001 20:36:47 +0100 (CET) Cc: Nils Holland , Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Matthew Dillon wrote: > This is great news! I'm crossing my fingers and hoping that Nils can't > reproduce the crash any more with Soren's fix. Me too :) I have a small change that can be used if performace suffers too badly, it has not provoked the problem again on any of the systems I've tried it on so far.: --- ata-pci.c 25 Dec 2001 14:44:26 -0000 1.24 +++ ata-pci.c 27 Dec 2001 17:24:32 -0000 @@ -97,9 +97,9 @@ if (pci_get_devid(child) == 0x03051106 || /* VIA KT133 */ pci_get_devid(child) == 0x03911106) { /* VIA KX133 */ - pci_write_config(child, 0x75, 0x83, 1); + pci_write_config(child, 0x75, 0x80, 1); pci_write_config(child, 0x76, - (pci_read_config(child, 0x76, 1) & 0xdf) | 0xd0,1); + (pci_read_config(child, 0x76, 1) & 0xf) | 0xd0, 1); device_printf(dev, "VIA '686b southbridge fix applied\n"); break; } > I'm also wondering how applicable this patch might be in regards to > forcing a 'safe' mode for other PCI chipsets, to allow us to test > it on non-686B machines that have similar problems. This patch is specific for VIA K[TX]133 northbridges together with the 686B southbridge. There might be issues with other new VIA chipsets that uses the 686B or derivatives, but I have no way to test that as I dont have any of that HW here in the lab. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 11:39:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 96DF237B417 for ; Thu, 27 Dec 2001 11:39:10 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id LAA25521; Thu, 27 Dec 2001 11:39:08 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda25519; Thu Dec 27 11:39:06 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.6/8.9.1) id fBRJd0t64505; Thu, 27 Dec 2001 11:39:00 -0800 (PST) Received: from UNKNOWN(10.1.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdz64502; Thu Dec 27 11:38:08 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.6/8.9.1) id fBRJc8N35049; Thu, 27 Dec 2001 11:38:08 -0800 (PST) Message-Id: <200112271938.fBRJc8N35049@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdO35044; Thu Dec 27 11:37:51 2001 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Matthias Andree Cc: freebsd-stable@FreeBSD.ORG Subject: Re: tcpd not installed on 4.5-PRERELEASE In-reply-to: Your message of "27 Dec 2001 20:30:49 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Dec 2001 11:37:51 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Matthias Andree writes: > Cy Schubert - ITSD Open Systems Group writes: > > > In message , Matthias Andree writes: > > > Hello, > > > > > > I just cleandir'ed out my whole /usr/obj/src and rebuilt the world > > > (4.5-PRERELEASE), installed it, and figured that tcpd seems to be > > > missing from the install, while tcpdchk and tcpdmatch are > > > installed. What's up here? Did I do something wrong? Is this worth a > > > send-pr? Or is tcpd just not part of the system? > > > > Tcpd is redundant under FreeBSD. FreeBSD's inetd uses libwrap > > (TCP/Wrapper library), effectively wrapping as if tcpd was in use. > > No, it is not redundant. > > I might have a different super-server than FreeBSD's inetd (tcpserver > from DJB's ucspi-tcp!), or I might want to run a service without libwrap > for efficiency reasons -- in that case, I'd have to run tcpd explicitly > for the other services. IMO, that's why we have the tcp_wrapper port. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD Ministry of Management Services Province of BC FreeBSD UNIX: cy@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 11:45:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from krusty.e-technik.uni-dortmund.de (krusty.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by hub.freebsd.org (Postfix) with ESMTP id D55B237B405 for ; Thu, 27 Dec 2001 11:45:06 -0800 (PST) Received: from emma1.emma.line.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1]) by krusty.e-technik.uni-dortmund.de (Postfix) with ESMTP id 4DE2FA3826 for ; Thu, 27 Dec 2001 20:45:05 +0100 (CET) Received: by emma1.emma.line.org (Postfix, from userid 500) id 8C1CCA2003; Thu, 27 Dec 2001 20:45:00 +0100 (CET) Date: Thu, 27 Dec 2001 20:45:00 +0100 From: Matthias Andree To: Cy Schubert - ITSD Open Systems Group Cc: Matthias Andree , freebsd-stable@FreeBSD.ORG Subject: Re: tcpd not installed on 4.5-PRERELEASE Message-ID: <20011227194500.GA28491@emma1.emma.line.org> References: <200112271938.fBRJc8N35049@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <200112271938.fBRJc8N35049@cwsys.cwsent.com> User-Agent: Mutt/1.3.24i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 27 Dec 2001, Cy Schubert - ITSD Open Systems Group wrote: > In message , Matthias Andree writes: > > Cy Schubert - ITSD Open Systems Group writes: > > > > > Tcpd is redundant under FreeBSD. FreeBSD's inetd uses libwrap > > > (TCP/Wrapper library), effectively wrapping as if tcpd was in use. > > > > No, it is not redundant. > > > > I might have a different super-server than FreeBSD's inetd (tcpserver > > from DJB's ucspi-tcp!), or I might want to run a service without libwrap > > for efficiency reasons -- in that case, I'd have to run tcpd explicitly > > for the other services. > > IMO, that's why we have the tcp_wrapper port. Won't work: bash-2.05a# pwd ; make install clean /usr/ports/security/tcp_wrapper ===> tcp_wrappers-7.6_1 is forbidden: tcp_wrappers is in the base system. ===> Cleaning for tcp_wrappers-7.6_1 (I presume the port is not redundant, older systems may rely on that.) I'm filing a PR now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 11:49:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pr0n.kutulu.org (pr0n.kutulu.org [151.196.107.157]) by hub.freebsd.org (Postfix) with ESMTP id B67E437B417 for ; Thu, 27 Dec 2001 11:49:35 -0800 (PST) Received: by pr0n.kutulu.org (Postfix, from userid 1000) id 8F7FD103; Thu, 27 Dec 2001 14:51:24 -0500 (EST) Date: Thu, 27 Dec 2001 14:51:24 -0500 From: Kutulu To: "Peter/Los Angeles, CA" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /usr/local/etc/rc.d/apache.sh question Message-ID: <20011227145124.A4869@pr0n.kutulu.org> Mail-Followup-To: "Peter/Los Angeles, CA" , freebsd-stable@FreeBSD.ORG References: <004001c18efd$5627bf00$245b1486@hhlaw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004001c18efd$5627bf00$245b1486@hhlaw.com>; from peter@haloflightleader.net on Thu, Dec 27, 2001 at 09:38:40AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 27, 2001 at 09:38:40AM -0800, Peter/Los Angeles, CA wrote: > [09:37][root@interim:/usr/local/etc/rc.d]# ls > apache.sh* > [09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start > ./apache.sh: Cannot determine the PREFIX Check the top few lines of apache.sh. It checks for it's own path prefix to figure out where "/usr/local" really is. Start it with the whole pathname like rc would do at boot: /usr/local/etc/rc.d/apache.sh start --K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 12:20:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pc1-cove4-0-cust214.bir.cable.ntl.com (pc1-cove4-0-cust214.bir.cable.ntl.com [213.105.93.214]) by hub.freebsd.org (Postfix) with ESMTP id B8F3A37B417; Thu, 27 Dec 2001 12:20:32 -0800 (PST) Received: (from root@localhost) by pc1-cove4-0-cust214.bir.cable.ntl.com (8.11.6/8.11.6) id fBRKKUu00767; Thu, 27 Dec 2001 20:20:30 GMT (envelope-from ianjhart@ntlworld.com) Received: from ntlworld.com (alpha.private.net [192.168.0.2]) (authenticated) by pc1-cove4-0-cust214.bir.cable.ntl.com (8.11.6/8.11.6av) with ESMTP id fBRKKF400760 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Thu, 27 Dec 2001 20:20:20 GMT (envelope-from ianjhart@ntlworld.com) Message-ID: <3C2B827F.6854604D@ntlworld.com> Date: Thu, 27 Dec 2001 20:20:15 +0000 From: ian j hart X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: sos@freebsd.dk Cc: Matthew Dillon , Matthew Gilbert , freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers References: <200112270938.fBR9cOQ95619@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Filter-Version: 1.7 (pc1-cove4-0-cust214.bir.cable.ntl.com) X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG SXren Schmidt wrote: > > It seems Matthew Dillon wrote: > > Sorry, I meant I'd follow up with Matthew Gilbert. Also, I've > > been trying to track down a crash in nfs_node that Nils Holland > > has been having - he appears to have the same chipset and could > > have the same problem, and he can reproduce the panic very consistently > > within a few hours. > > > > Brady has an older chipset. Are there any known problems with this > > chipset? > > Nope... > > > pcib1: at device 1.0 on pci0 > > pci1: on pcib1 > > isab0: at device 7.0 on pci0 > > isa0: on isab0 > > atapci0: port 0xe400-0xe40f at device 7.1 on pci0 > > -Søren > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Oh yes there are Myself and others have had IDE related problems. Search the stable and hardware mail archives for UDMA and ICRC [and ianjhart] for examples. There is also the "only supports 16MxN RAM" feature. -- ian j hart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 12:25:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vortex.wa4phy.net (cc449817-a.mrtnz1.ga.home.com [24.12.79.51]) by hub.freebsd.org (Postfix) with ESMTP id 5EEF637B416 for ; Thu, 27 Dec 2001 12:25:17 -0800 (PST) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.11.6/8.11.6) with ESMTP id fBRKP8157798; Thu, 27 Dec 2001 15:25:08 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3C2B83A4.1E1FCCC1@vortex.wa4phy.net> Date: Thu, 27 Dec 2001 15:25:08 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-PRERELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: Joe Clarke Cc: freebsd-stable@FreeBSD.ORG, Cy.Schubert@uumail.gov.bc.ca Subject: Re: Gnome References: <20011227140812.P11529-100000@shumai.marcuscom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks Guys.. I'll give it a shot and see what happens.. didn't want to clutter up with output from make, but in short, it appears to be some new capplet .. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 12:33: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shumai.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id AC6C637B42C for ; Thu, 27 Dec 2001 12:32:59 -0800 (PST) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.6/8.11.6) with ESMTP id fBRKXEH13602; Thu, 27 Dec 2001 15:33:14 -0500 (EST) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Thu, 27 Dec 2001 15:33:13 -0500 (EST) From: Joe Clarke To: Sam Drinkard Cc: freebsd-stable@FreeBSD.ORG, Subject: Re: Gnome In-Reply-To: <3C2B83A4.1E1FCCC1@vortex.wa4phy.net> Message-ID: <20011227153246.B11529-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 27 Dec 2001, Sam Drinkard wrote: > Thanks Guys.. I'll give it a shot and see what happens.. didn't want to > clutter up with output from make, but in short, it appears to be some > new capplet .. If you still have problems after the uninstall/reinstall, pick this topic up on freebsd-gnome@. Joe > > Sam > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 12:51:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from voi.aagh.net (pc1-hart4-0-cust168.mid.cable.ntl.com [62.254.84.168]) by hub.freebsd.org (Postfix) with ESMTP id 40BB037B416 for ; Thu, 27 Dec 2001 12:51:41 -0800 (PST) Received: from freaky by voi.aagh.net with local (Exim 3.33 #1) id 16JhV5-000LcK-00 for freebsd-stable@FreeBSD.ORG; Thu, 27 Dec 2001 20:51:39 +0000 Date: Thu, 27 Dec 2001 20:51:39 +0000 From: Thomas Hurst To: freebsd-stable@FreeBSD.ORG Subject: Re: /usr/local/etc/rc.d/apache.sh question Message-ID: <20011227205139.GA82499@voi.aagh.net> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <004001c18efd$5627bf00$245b1486@hhlaw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004001c18efd$5627bf00$245b1486@hhlaw.com> User-Agent: Mutt/1.3.24i Organization: Not much. X-Operating-System: FreeBSD/4.5-PRERELEASE (i386) X-Uptime: 8:45PM up 7 days, 5:30, 4 users, load averages: 2.06, 2.03, 2.00 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Peter/Los Angeles, CA (peter@haloflightleader.net) wrote: > ./apache.sh: Cannot determine the PREFIX > if ! PREFIX=$(expr $0 : "\(/.*\)/etc/rc\.d/$(basename $0)\$"); then > echo "$0: Cannot determine the PREFIX" >&2 Note that $0 (argv[0] in C, i.e. the 'zeroth' argument) is the filename the program was called as. In this case it's trying to work out what the prefix is (/usr/local, /usr/pkg, etc), by looking at how it was called; since yours is unlikely to change you can replace it with a simple 'PREFIX=/usr/local', which will let you call it as ./apache.sh. With apache, though, I usually just use apachectl; apachectl start Wish more daemons would come with programs like that :) -- Thomas 'Freaky' Hurst - freaky@aagh.net - http://www.aagh.net/ - Your computer account is overdrawn. Please reauthorize. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 13:23:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.136.200]) by hub.freebsd.org (Postfix) with ESMTP id F2B5F37B417; Thu, 27 Dec 2001 13:23:34 -0800 (PST) Received: from pyanfar.ece.cmu.edu (pqgljsjqbfd15wwu@VPN85.ECE.CMU.EDU [128.2.138.85]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id fBRLNLZ14034; Thu, 27 Dec 2001 16:23:21 -0500 (EST) Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers From: "Brandon S. Allbery " KF8NH To: ian j hart Cc: sos@freebsd.dk, Matthew Dillon , Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <3C2B827F.6854604D@ntlworld.com> References: <200112270938.fBR9cOQ95619@freebsd.dk> <3C2B827F.6854604D@ntlworld.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0 (Preview Release) Date: 27 Dec 2001 16:23:18 -0500 Message-Id: <1009488203.2943.2.camel@vpn85.ece.cmu.edu> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2001-12-27 at 15:20, ian j hart wrote: > Myself and others have had IDE related problems. Search > the stable and hardware mail archives for > UDMA and ICRC [and ianjhart] for examples. > > There is also the "only supports 16MxN RAM" feature. Maybe I should toss in that I've had spontaneous reboots during heavy IDE activity both on my desktop (VIA 82C686) and my laptop (Intel 82443BX). And before that, random disk corruption during heavy SCSI activity on my old desktop machine (seen with Tekram and Acer 83C575-based host adapters and a borrowed Adaptec 2940). -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 13:54:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from digital.csudsu.com (digital.csudsu.com [209.249.57.102]) by hub.freebsd.org (Postfix) with ESMTP id DBB4D37B41A for ; Thu, 27 Dec 2001 13:54:01 -0800 (PST) Received: by digital.csudsu.com (Postfix, from userid 1000) id 3F6A022E02; Thu, 27 Dec 2001 13:53:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by digital.csudsu.com (Postfix) with ESMTP id 307E51F003; Thu, 27 Dec 2001 13:53:57 -0800 (PST) Date: Thu, 27 Dec 2001 13:53:57 -0800 (PST) From: Stefan Molnar To: Matthias Andree Cc: Cy Schubert - ITSD Open Systems Group , Matthias Andree , Subject: Re: tcpd not installed on 4.5-PRERELEASE In-Reply-To: <20011227194500.GA28491@emma1.emma.line.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG That is not a bug. It is there to notify people that it is in the base. Edit the Makefile and remove the FORBIDDEN line, then you are good to go. On Thu, 27 Dec 2001, Matthias Andree wrote: > On Thu, 27 Dec 2001, Cy Schubert - ITSD Open Systems Group wrote: > > > In message , Matthias Andree writes: > > > Cy Schubert - ITSD Open Systems Group writes: > > > > > > > Tcpd is redundant under FreeBSD. FreeBSD's inetd uses libwrap > > > > (TCP/Wrapper library), effectively wrapping as if tcpd was in use. > > > > > > No, it is not redundant. > > > > > > I might have a different super-server than FreeBSD's inetd (tcpserver > > > from DJB's ucspi-tcp!), or I might want to run a service without libwrap > > > for efficiency reasons -- in that case, I'd have to run tcpd explicitly > > > for the other services. > > > > IMO, that's why we have the tcp_wrapper port. > > Won't work: > > bash-2.05a# pwd ; make install clean > /usr/ports/security/tcp_wrapper > ===> tcp_wrappers-7.6_1 is forbidden: tcp_wrappers is in the base system. > ===> Cleaning for tcp_wrappers-7.6_1 > > (I presume the port is not redundant, older systems may rely on that.) > > I'm filing a PR now. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 14: 4: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 4650737B420; Thu, 27 Dec 2001 14:03:55 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id fBRM3ep79889; Thu, 27 Dec 2001 23:03:40 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200112272203.fBRM3ep79889@freebsd.dk> Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers In-Reply-To: <1009488203.2943.2.camel@vpn85.ece.cmu.edu> To: "Brandon S. Allbery KF8NH" Date: Thu, 27 Dec 2001 23:03:40 +0100 (CET) Cc: ian j hart , Matthew Dillon , Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Brandon S. Allbery KF8NH wrote: > On Thu, 2001-12-27 at 15:20, ian j hart wrote: > > Myself and others have had IDE related problems. Search > > the stable and hardware mail archives for > > UDMA and ICRC [and ianjhart] for examples. > > > > There is also the "only supports 16MxN RAM" feature. > > Maybe I should toss in that I've had spontaneous reboots during heavy > IDE activity both on my desktop (VIA 82C686) and my laptop (Intel > 82443BX). And before that, random disk corruption during heavy SCSI > activity on my old desktop machine (seen with Tekram and Acer > 83C575-based host adapters and a borrowed Adaptec 2940). Guys guys, we are talking about known HW issues that causes known bad behavior, having a system that is flaky can have all kinds of reasons, I'd risk saying that genuine HW bugs like the 686B bug is one of the least likely problems... The most likely reasons are probably bad/subspec'd RAM, lousy PSU, bad/subspec'd cabeling, too many "performance features" enabled, generally crappy hardware (there are *tons* of that out there), bad/insufficient cooling, overclocking (even the motherboard makers overclock pr default nowadays to gain a litte over the competition), And do *not* forget bugs/bogons/mistakes in your favorite OS :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 14: 5: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from krusty.e-technik.uni-dortmund.de (krusty.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by hub.freebsd.org (Postfix) with ESMTP id D7F1E37B437 for ; Thu, 27 Dec 2001 14:04:47 -0800 (PST) Received: from emma1.emma.line.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1]) by krusty.e-technik.uni-dortmund.de (Postfix) with ESMTP id 1D198A3826 for ; Thu, 27 Dec 2001 23:04:45 +0100 (CET) Received: by emma1.emma.line.org (Postfix, from userid 500) id BA42AA2003; Thu, 27 Dec 2001 23:04:44 +0100 (CET) Date: Thu, 27 Dec 2001 23:04:44 +0100 From: Matthias Andree To: freebsd-stable@FreeBSD.ORG Subject: Re: tcpd not installed on 4.5-PRERELEASE Message-ID: <20011227220444.GA7153@emma1.emma.line.org> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <20011227194500.GA28491@emma1.emma.line.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.24i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 27 Dec 2001, Stefan Molnar wrote: > That is not a bug. It is there to notify people that it is in the base. > Edit the Makefile and remove the FORBIDDEN line, then you are good to go. > > On Thu, 27 Dec 2001, Matthias Andree wrote: > > > bash-2.05a# pwd ; make install clean > > /usr/ports/security/tcp_wrapper > > ===> tcp_wrappers-7.6_1 is forbidden: tcp_wrappers is in the base system. > > ===> Cleaning for tcp_wrappers-7.6_1 > > > > (I presume the port is not redundant, older systems may rely on that.) > > > > I'm filing a PR now. Please put the quote first, then your text, to maintain a (chrono)logical order. I'm well aware that the FORBIDDEN line is a feature, not a bug, and I filed the PR against the base system which doesn't install tcpd. See PR #33257. -- Matthias Andree "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 14:39:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id C7EAB37B419 for ; Thu, 27 Dec 2001 14:38:27 -0800 (PST) Received: from attbi.com ([12.237.33.57]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011227223827.JXQM6450.rwcrmhc52.attbi.com@attbi.com> for ; Thu, 27 Dec 2001 22:38:27 +0000 Message-ID: <3C2BA2FC.FC5D658D@attbi.com> Date: Thu, 27 Dec 2001 16:38:52 -0600 From: Joe Halpin X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: USB camera Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm not able to mount my USB camera. This is what dmesg has to say about my usb port: $ dmesg | grep -i usb uhci0: port 0xe000-0xe01f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 bash-2.05$ dmesg | grep -i scsi da0: Removable Direct Access SCSI-2 device da0: Removable Direct Access SCSI-2 device This is what /var/log/messages says when I plug the camera in and turn it on: Dec 27 15:41:01 fbsd /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Dec 27 15:41:01 fbsd /kernel: da0: Removable Direct Access SCSI-2 device Dec 27 15:41:01 fbsd /kernel: da0: 650KB/s transfers Dec 27 15:41:01 fbsd /kernel: da0: 15MB (31808 512 byte sectors: 64H 32S/T 15C) Dec 27 15:47:13 fbsd /kernel: umass0: at uhub0 port 1 (addr 2) disconnected Dec 27 15:47:13 fbsd /kernel: (da0:umass-sim0:0:0:0): lost device Dec 27 15:47:13 fbsd /kernel: (da0:umass-sim0:0:0:0): removing device entry Dec 27 15:47:13 fbsd /kernel: umass0: detached On my Linux box I just mount the device file and the camera shows up as a filesystem. Is it different in FreeBSD? Thanks Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 14:40:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 50D5537B437 for ; Thu, 27 Dec 2001 14:39:56 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBRMdtj89631; Thu, 27 Dec 2001 14:39:55 -0800 (PST) (envelope-from dillon) Date: Thu, 27 Dec 2001 14:39:55 -0800 (PST) From: Matthew Dillon Message-Id: <200112272239.fBRMdtj89631@apollo.backplane.com> To: Andrew Stuart Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Via 686B southbrige corruption.. References: <20011227105219.A30619@freebsd.tekrealm.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :i dont have a via686b chipset.. but am having simular issues.. :i can repeatedly panic the system by transfering large amounts :of files from a pci adaptec 29160 to a ide harddrive, and also :ide to ide harddrive.. : :pcib2: at device 1.0 :on pci0 :atapci0: port 0xd000-0xd00f at device 7.1 :on pci0 :ata0: at 0x1f0 irq 14 on atapci0 :ata1: at 0x170 irq 15 on atapci0 :ahc0: port 0xdc00-0xdcff mem :0xe310a000-0xe310afff irq 5 at device 18.0 on pci0 :aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs :ad0: 39082MB [79406/16/63] at ata0-master UDMA66 :da0 at ahc0 bus 0 target 0 lun 0 :da0: Fixed Direct Access SCSI-3 device :da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged :Queueing Enabled :da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) : :i have also tested going from scsi to scsi and dont seem to have :the issue. this is on known good hardware. : :-- :Andrew This is similar to the chipset that Brady has. Same bridge chip anyway. pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe400-0xe40f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xe000-0xe01f irq 5 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 14:45: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6E37037B405 for ; Thu, 27 Dec 2001 14:45:03 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBRMj0q89695; Thu, 27 Dec 2001 14:45:00 -0800 (PST) (envelope-from dillon) Date: Thu, 27 Dec 2001 14:45:00 -0800 (PST) From: Matthew Dillon Message-Id: <200112272245.fBRMj0q89695@apollo.backplane.com> To: Alexey G Misurenko Cc: freebsd-stable@freebsd.org Subject: Re: nfs References: <3C2B05D2.7020708@caravan.ru> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :" :DESCRIPTION : rpc.umntall is as command as proposed in the NFS RPC specification; see : NFS Version 3 Protocol Specification, RFC 1813, Appendix I. It uses : remote procedure calls to remove mount entries from : /var/db/mountdtab on the remote NFS server. It is called : automatically without any parameters during startup and shutdown of : the system. This ensures that showmount(8) does not display old : and expired entries. The rpc.umntall command is only needed on : client side, where mount_nfs(8) adds a mount entry with the current : date to /var/db/mounttab, and umount(8) removes the entry again. : The rpc.umntall command cares about all remaining entries in this : table which result from crashes or unproper shutdowns. :" : : : but if analize /etc/rc* scripts we can see that :*rpc.umntall* is called on network_pass3 which is called after :the nfsclient allready mount fs exported by nfs server. : And we think that this is problems when nfs client return online :after crash. Because in this case nfs server don't know any think about :crash event of its client. : :p.s. sorry for badly english :-- :WBR, Alexey G Misurenko ( MAG-RIPE | MMAGG-RIPN ) I don't think we can reorder that, because rpc.umntall itself is on /usr which might be NFS mounted. I don't consider it a big deal that the server is not notified of the crash... the server doesn't really care anyway and the NFSv2/v3 spec have no provisions for active server state. It is merely a convenience. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 14:48:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wolfram.com (wri-dns0.wolfram.com [140.177.205.10]) by hub.freebsd.org (Postfix) with ESMTP id 5898837B419 for ; Thu, 27 Dec 2001 14:48:45 -0800 (PST) Received: from wopr.wolfram.com (wopr.wolfram.com [140.177.10.29]) by wolfram.com (8.11.2/8.11.2) with ESMTP id fBRMmcw13340 for ; Thu, 27 Dec 2001 16:48:39 -0600 Received: from localhost (josht@localhost) by wopr.wolfram.com (8.9.3/8.9.3) with ESMTP id QAA06355 for ; Thu, 27 Dec 2001 16:48:36 -0600 Date: Thu, 27 Dec 2001 16:48:36 -0600 (CST) From: Josh Tolbert To: freebsd-stable@FreeBSD.ORG Subject: Problem with /usr/ports/graphics/glide3 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a working X 4.1.0/DRI setup for my voodoo3/3000 at home (documentation of how I managed to get it working is at http://halcyon.scoundrelz.net/~hemi/dri.txt). I found a PC at work and decided I'd try to replicate my X 4.1.0/DRI setup at work. X installed fine from ports and /usr/ports/graphics/glide3 downloaded fine. I applied anholt's patch from ports/31767. On build (make -DWITH_VOODOO3=1 install), I get errors such as the following, with stop errors afterwards: automake: configure.in: required file `./depcomp' not found automake: cvg/glide3/src/makefile.autoconf.am: Assembler source seen but `ASFLAGS' not defined in `configure.in' automake: h3/glide3/src/makefile.autoconf.am: object `cpudtect.lo' created by `cpudtect.c' and `cpudtect.S' automake: h3/glide3/src/makefile.autoconf.am: object `cpudtect.lo' created by `cpudtect.c' and `cpudtect.S' automake: h3/glide3/src/makefile.autoconf.am: object `cpudtect.lo' created by `cpudtect.c' and `cpudtect.S' automake: h3/glide3/src/makefile.autoconf.am: object `cpudtect.lo' created by `cpudtect.c' and `cpudtect.S' automake: h3/glide3/src/makefile.autoconf.am: Assembler source seen but `ASFLAGS' not defined in `configure.in' and similar errors for h5/*. I don't see that ./depcomp file anywhere in the work/Glide3 dir and my /etc/make.conf is fairly normal: CPUTYPE, CFLAGS, CXXFLAGS, XFREE86_VERSION=4, NOPROFILE=true and USA_RESIDENT=YES is about all that is in /etc/make.conf. I have the required dependencies installed (including autoconf213-2.13.000227_1 and automake-1.5,1. I tried removing anholt's patch and building the port but the problem remains. The machine is a fresh install of 4.4-R with a world/kernel built early this morning. FreeBSD polarbear.XXXX 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #0: Thu Dec 27 01:42:08 CST 2001 root@polarbear.XXXX:/usr/obj/usr/src/sys/POLARBEAR i386 Any help would be greatly appreciated...Some of the linux guys here are having a field day with my troubles. Thanks ------------ ---- -- Josh Tolbert josht@wolfram.com Help Desk, Wolfram Research, Inc. 217-397-0700x246 :1dG:wq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 14:50:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2E43637B62B for ; Thu, 27 Dec 2001 14:50:50 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBRMnRY89738; Thu, 27 Dec 2001 14:49:27 -0800 (PST) (envelope-from dillon) Date: Thu, 27 Dec 2001 14:49:27 -0800 (PST) From: Matthew Dillon Message-Id: <200112272249.fBRMnRY89738@apollo.backplane.com> To: Volker Stolz Cc: stable@FreeBSD.ORG Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers References: <200112202333.fBKNXZ679605@apollo.backplane.com> <29650.193.88.88.10.1008956812.squirrel@webmail.jkkn.net> <200112211930.fBLJUs988388@apollo.backplane.com> <200112261924.fBQJORF47150@apollo.backplane.com> <20011227111021.A10171@i2.informatik.rwth-aachen.de> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :My Gigabyte 6BXD has Intel's BX chipset. :But yesterday it threw up with 'panic: ufsdirrehash'(?) instead of a general :page fault, but I didn't reach the console in time to prevent an auto- :matic reboot and get the full message :-/ :I'll post the dmesg as soon as I get home. :-- :Wonderful \hbox (0.80312pt too nice) in paragraph at lines 16--18 :Volker Stolz * stolz@i2.informatik.rwth-aachen.de :Please use PGP or S/MIME for correspondence! Well, judging from your last few postings I think your problem is unrelated to the IDE and 686B issues we've been discussing. It really sounds like there is something seriously broken on your machine. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 15:20: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from postfix2-2.free.fr (postfix2-2.free.fr [213.228.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 37D1E37B416 for ; Thu, 27 Dec 2001 15:19:55 -0800 (PST) Received: from graf.pompo.net (lyon-1-a7-17-77.dial.proxad.net [62.147.17.77]) by postfix2-2.free.fr (Postfix) with ESMTP id 104435F765 for ; Fri, 28 Dec 2001 00:19:53 +0100 (CET) Received: by graf.pompo.net (Postfix, from userid 1001) id 3D4B97871; Fri, 28 Dec 2001 00:21:05 +0100 (CET) Date: Fri, 28 Dec 2001 00:21:05 +0100 From: Thierry Thomas To: stable@FreeBSD.ORG Subject: swap_pager problem [was Re: 4.5 PRERELEASE - Call for testing] Message-ID: <20011228002105.A5991@graf.pompo.net> Mail-Followup-To: stable@FreeBSD.ORG References: <20011221163036.G1015@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20011221163036.G1015@windriver.com>; from murray@FreeBSD.ORG on Fri, Dec 21, 2001 at 04:30:37PM -0800 X-Operating-System: FreeBSD 4.5-PRERELEASE i386 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc;y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Le 21 Dec 01 à 16:30:37 +0000, Murray Stokely écrivait : > More than anything, we just need more users to run 4.5-PRERELEASE and > the upcoming release candidates and report any performance or > stability problems. Please help us make FreeBSD 4.5 our best > performing release ever! I have upgraded this morning from 4.4-stable to 4.5-prerelease (cvsup at 08:15 GMT). Everything was OK, until I get into a problem very similar to PR kern/30164: Dec 27 23:20:42 graf /kernel: sio0: 1 more silo overflow (total 284) Dec 27 23:23:48 graf /kernel: swap_pager: out of swap space Dec 27 23:23:48 graf /kernel: swap_pager_getswapspace: failed Dec 27 23:23:56 graf /kernel: pid 297 (XFree86), uid 0, was killed: out of swap space I was not running anything unusual (XFree4 + kde 2.2.2 with konqueror + 3 rxvt + one make fetch + mutt + one gcc for a middle-sized program), and before 4.5-prerelease I had never met such a problem. For info: #>pstat -s (after reboot!) Device 1K-blocks Used Avail Capacity Type /dev/ad0s3b 262016 0 262016 0% Interleaved -- Th. Thomas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 15:20:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vortex.wa4phy.net (cc449817-a.mrtnz1.ga.home.com [24.12.79.51]) by hub.freebsd.org (Postfix) with ESMTP id BFBB737B41A for ; Thu, 27 Dec 2001 15:20:03 -0800 (PST) Received: (from sam@localhost) by vortex.wa4phy.net (8.11.6/8.11.6) id fBRNK1203054 for freebsd-stable@freebsd.org; Thu, 27 Dec 2001 18:20:01 -0500 (EST) (envelope-from sam) From: Sam Drinkard Message-Id: <200112272320.fBRNK1203054@vortex.wa4phy.net> Subject: What a Can of Worms! To: freebsd-stable@freebsd.org Date: Thu, 27 Dec 2001 18:20:01 -0500 (EST) X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have to say it, since I asked the question here.. compiling gnome and all it's bits is not for the faint-hearted. I've been running makes for about 3 hours now, and it's still not done. Had to start clean once, because of a lib dependency but now all seems to be working OK.. hopefully I'll know soon if the whole mess works again. Next time somebody bitches about something not being in the packages section of a -release, send 'em to me.. I'll tell it like it is! To all the people who make -releases possible, my very sincere thanks to all the work and debugging that goes into one. I think next time, I'll just wait it out and grab the CD's. Gotta be lots less hair pulling. Now I'll shut up and leave things alone! Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 15:30:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from zircon.seattle.wa.us (sense-sea-CovadSub-0-228.oz.net [216.39.147.228]) by hub.freebsd.org (Postfix) with SMTP id 13A4F37B405 for ; Thu, 27 Dec 2001 15:30:42 -0800 (PST) Received: (qmail 26741 invoked by uid 1001); 27 Dec 2001 23:33:04 -0000 From: Joe Kelsey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15403.44976.318799.379419@zircon.zircon.seattle.wa.us> Date: Thu, 27 Dec 2001 15:33:04 -0800 To: Sam Drinkard , freebsd-stable@freebsd.org Subject: What a Can of Worms! In-Reply-To: <200112272320.fBRNK1203054@vortex.wa4phy.net> References: <200112272320.fBRNK1203054@vortex.wa4phy.net> X-Mailer: VM 6.98 under Emacs 21.1.1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sam Drinkard writes: > I have to say it, since I asked the question here.. compiling gnome > and all it's bits is not for the faint-hearted. I've been running > makes for about 3 hours now, and it's still not done. Had to start > clean once, because of a lib dependency but now all seems to be > working OK.. hopefully I'll know soon if the whole mess works again. Upgrading gnome is fraught with errors, due to inadequate port dependencies. The last time I tried, I ended up installing portupgrade first, then using portupgrade to simplify the process. It still takes forever, but at least I finally got a clean install for gnome 1.4. Go to /usr/ports/sysutile/portupgrade and install it. It really is a great tool to use for making ports. /Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 15:37:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hex.databits.net (hex.csh.rit.edu [129.21.60.203]) by hub.freebsd.org (Postfix) with SMTP id A7B1737B416 for ; Thu, 27 Dec 2001 15:37:54 -0800 (PST) Received: (qmail 26208 invoked by uid 1001); 27 Dec 2001 23:37:50 -0000 Date: Thu, 27 Dec 2001 18:37:50 -0500 From: Pete Fritchman To: Josh Tolbert Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Problem with /usr/ports/graphics/glide3 Message-ID: <20011227183750.A26126@databits.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from josht@wolfram.com on Thu, Dec 27, 2001 at 04:48:36PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ++ 27/12/01 16:48 -0600 - Josh Tolbert: | I have a working X 4.1.0/DRI setup for my voodoo3/3000 at home | (documentation of how I managed to get it working is at | http://halcyon.scoundrelz.net/~hemi/dri.txt). I found a PC at work and | decided I'd try to replicate my X 4.1.0/DRI setup at work. | | X installed fine from ports and /usr/ports/graphics/glide3 | downloaded fine. I applied anholt's patch from ports/31767. On build (make | -DWITH_VOODOO3=1 install), I get errors such as the following, with stop | errors afterwards: Is this still a problem without the patch? Are your automake/autoconf installations up to date? (There have been some recent major changes in this area). | Any help would be greatly appreciated...Some of the linux guys | here are having a field day with my troubles. Ask them if unmounting a partition under FreeBSD corrupts it if you're running a certain kernel :) -pete -- Pete Fritchman [petef@(databits.net|freebsd.org|csh.rit.edu)] finger petef@databits.net for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 27 15:40:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from jkkn.jkkn.net (cpe.atm2-0-1031198.0x503eea76.odnxx2.customer.tele.dk [80.62.234.118]) by hub.freebsd.org (Postfix) with ESMTP id B9DA137B416; Thu, 27 Dec 2001 15:39:17 -0800 (PST) Received: from JKKNLAPTOP (pc92187.stofanet.dk [212.10.12.187]) (authenticated) by jkkn.jkkn.net (8.11.6/8.11.6) with ESMTP id fBRNd4S08052; Fri, 28 Dec 2001 00:39:04 +0100 (CET) (envelope-from jkkn@jkkn.dk) Message-ID: <008d01c18f2f$ab983b40$bb5ca8c0@jkkn.net> From: "Kristian K. Nielsen" To: "Matthew Dillon" , "Nils Holland" Cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= , "Matthew Gilbert" , , References: <200112262355.fBQNtfK48250@apollo.backplane.com> <200112270945.fBR9j1e97273@freebsd.dk> <20011227163252.A151@tisys.org> <200112271847.fBRIlxh52129@apollo.backplane.com> Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers Date: Fri, 28 Dec 2001 00:39:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Disposition-Notification-To: "Kristian K. Nielsen" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey, It is great if you are finding a solution for the VIA-chipset. Do you have any idea if it is a simular problem that I am experiencing? I am not enough into chip code to have a clue what exactly the patch is doing - but maybe it is just decreasing the load on the kernel/system in a way that the crashes are avoided tough there is still a bug outthere somewhere?! I do not have a single VIA-chip in my box that I know of - all Intel and is running the latest BIOS version avialable for my motherboard and still having crashes whenever I put any pressure on the box, like compiling/moving large files across filesystems/etc: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-STABLE #0: Fri Dec 7 14:21:48 CET 2001 jkkn@jkkn.jkkn.net:/usr/src/sys/compile/JKKN_KRNL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300683283 Hz CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping = 4 Features=0x80f9ff real memory = 402640896 (393204K bytes) avail memory = 387928064 (378836K bytes) Preloaded elf kernel "kernel" at 0xc02ff000. Pentium Pro MTRR support enabled Using $PIR table, 6 entries at 0xc00f0d10 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 12 chip1: port 0xe800-0xe80f at device 4.3 on pci0 rl0: port 0xd000-0xd0ff mem 0xe3000000-0xe30000ff irq 10 at device 10.0 on pci0 rl0: Ethernet address: 00:40:95:30:2e:5e miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at 12.0 irq 11 orm0: [±¤°í]¹®±¸°¡ µé¾î°£ ¸ÞÀÏÀ» 100% Â÷´ÜÇÏ´Â ¹æ¹ý !!

[±¤°í]¹®±¸°¡ µé¾î°£ ¸ÞÀÏÀ» 100% Â÷´ÜÇϴ¹ý !!

ÄÄÀ» ¾Ë°í³ª¸é ½ºÆÔ¸ÞÀÏ °ÆÁ¤¾ÈÇÏ°í ¾ó¸¶µçÁö ¸ÞÀÏÀ» ÀÌ¿ëÇÒ ¼ö°¡ ÀÖÁö¿©~

À¥¸ÞÀÏ ¸Þ´ºÁß È¯°æ¼³Á¤À̳ª¿É¼Ç¼±Åà - ÇÊÅͼ±ÅÃÈÄ - [±¤°í]¹®±¸¸¦ ¼ö½Å°ÅºÎ¿¡ Ãß°¡ÇÏ¸é ´ÙÀ½ºÎÅÍ Á¦¸ñ¿¡ [±¤°í]¶ó´Â ¹®±¸°¡ µé¾î°£ ¸ÞÀÏ°ú ¿µ¿øÈ÷ À̺°À» ÇÒ ¼ö ÀÖ´ä´Ï´Ù..^^    (¿åÀ» Çϰųª ½Å°í¸¸À¸·Ð ÀüÇô È¿°ú°¡ ¾øÀ½)

¸ðµç À¥¸ÞÀÏ¿¡´Â ½ºÆÔÂ÷´Ü ±â´É¿Ü ½È¾îÇÏ´Â ¸ÞÀϸ¸ ¸·À» ¼ö ÀÖ´Â ±â´ÉÀÌ ÀÖÀ¸¸ç .. ¼ºÀÎ, ¼îÇÎ, CD, µ¿¿µ»ó µî... ¹Þ±â½ÈÀº ³»¿ëÀÌ µé¾î°£ °Í¸¸ °ÅºÎÇÒ ¼öµµ Àִµ¥ Á¶±Ý¸¸ ½Å°æ¾²¸é [±¤°í]¸ÞÀÏ °ÆÁ¤ ¶Ò...!! °£´ÜÇÏÁÒ...^ ^

¸¸¾à Á¦¸ñ¿¡ [±¤°í]¶ó´Â ¹®±¸°¡ ¾ø´Ù¸é º»¹®¿¡ "¼ö½Å°ÅºÎ"¶õ ¹®±¸¸¦ ÇÊÅ͸µÀ¸·Î Çغ¸¼¼¿ä ±×·³ ±¤°í¸ÞÀÏÀº ¸ø µé¾î¿À°í ÈÞÁöÅëÀ¸·Î »ç¶óÁý´Ï´Ù
 (Áï ±¤°í¸ÞÀÏÀº º»¹®¿¡ "¼ö½Å°ÅºÎ¸¦ ÇØÁÖ¼¼¿ä µî... Á˼ÛÇÕ´Ï´Ù µîÀÇ ¹®±¸°¡ ÀÖÀ¸´Ï ±× ¹®±¸¸¦ Æ÷ÇÔÇÑ °ÍÀº ¸ðµÎ ¸·¾Æ ÁÝ´Ï´Ù )

»õ·Î¿î µµ¸ÞÀÎ µî·Ï¾È³»...¹ÙÀÌ·¯½º °æ°í¾È³»...»õ·Î¿î ½Å»óÇ°À» ½Ñ °¡°Ý¿¡ ±¸ÀÔÇÒ ¼ö ÀÖ´Â ¼îÇθô...°ü±¤¾È³»...Çпø¾È³»...°¢Á¾Á¤º¸ ¼Ò½ÄÁö...¼ºÀÎ...µî...±× ¸ðµÎ¸¦ [±¤°í]¶ó°í ÇÏÁö¿ä~

±×¸®°í ¼ö½ÅÀÚµéÁß 60%°¡ ±¤°í¸ÞÀÏ¿¡ ÀÇÇØ ¼ö¸¹Àº Á¤º¸¸¦ ¾ò´Â´Ù°í ÇÕ´Ï´Ù, ¼ö¸¹Àº ±¤°íµé Áß ²À ±× Á¤º¸¸¦ ÇÊ¿ä·Î ÇÏ´Â ºÐµµ °è½Ã´Ù´Â »ç½Ç ¶§¹®¿¡ ±¤°í´Â Á¸ÀçÇÏ´Â °ÍÀÔ´Ï´Ù

±×¸®°í ÀÌ ¾î·Á¿î ½Ã´ë¿¡ »ì¾Æ³²±â À§ÇØ ¸öºÎ¸²Ä¡´Â ºÐµéÀ» À§ÇØ ÀÚ±âÁý ¹®´Ü¼ÓÀ» ÇÏ´ÂÀǹ̿¡¼­ [±¤°í] ÇÊÅ͸µ ¼±ÅÃÇϽÉÀÌ ¾î¶³·±Áö¿ä~~
±¤°íÁֵ鵵 ´õºÒ¾î »ì¾Æ°¡´Â »ç¶÷µéÀ̴ϱî¿ä

±¤°í¸¦ ÇÊ¿ä·Î ÇÏ´Â »ç¶÷¸¸ º¸±â¸¦ ¹Ù¶ó´Â ¸¶À½¿¡¼­....

¹«·á¼ºÀοµÈ­º¸±â

¹«·á¼ºÀθ¸È­º¸±â

 

  - ÃÖÈÄÀÇ Èñ¸ÁÀº ±àÁ¤ÀûÀÎ »ç°í¹æ½Ä ±×¸®°í »ç¶û... -

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 29 13:54:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lycos.co.kr (catv-kwangjoo-210205028145.usr2.hananet.net [210.205.28.145]) by hub.freebsd.org (Postfix) with SMTP id 30EC537B427 for ; Sat, 29 Dec 2001 13:53:08 -0800 (PST) Reply-To: adfree114@lycos.co.kr From: adfree114 To: Subject: [±¤°í]¹®±¸°¡ µé¾î°£ ¸ÞÀÏÀ» 100% Â÷´ÜÇϴ¹ý !! Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Sun, 30 Dec 2001 06:54:47 +0900 X-Priority: 3 X-Mailer: Mailtouch 1.0 Message-Id: <20011229215308.30EC537B427@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [±¤°í]¹®±¸°¡ µé¾î°£ ¸ÞÀÏÀ» 100% Â÷´ÜÇÏ´Â ¹æ¹ý !!

[±¤°í]¹®±¸°¡ µé¾î°£ ¸ÞÀÏÀ» 100% Â÷´ÜÇϴ¹ý !!

ÄÄÀ» ¾Ë°í³ª¸é ½ºÆÔ¸ÞÀÏ °ÆÁ¤¾ÈÇÏ°í ¾ó¸¶µçÁö ¸ÞÀÏÀ» ÀÌ¿ëÇÒ ¼ö°¡ ÀÖÁö¿©~

À¥¸ÞÀÏ ¸Þ´ºÁß È¯°æ¼³Á¤À̳ª¿É¼Ç¼±Åà - ÇÊÅͼ±ÅÃÈÄ - [±¤°í]¹®±¸¸¦ ¼ö½Å°ÅºÎ¿¡ Ãß°¡ÇÏ¸é ´ÙÀ½ºÎÅÍ Á¦¸ñ¿¡ [±¤°í]¶ó´Â ¹®±¸°¡ µé¾î°£ ¸ÞÀÏ°ú ¿µ¿øÈ÷ À̺°À» ÇÒ ¼ö ÀÖ´ä´Ï´Ù..^^    (¿åÀ» Çϰųª ½Å°í¸¸À¸·Ð ÀüÇô È¿°ú°¡ ¾øÀ½)

¸ðµç À¥¸ÞÀÏ¿¡´Â ½ºÆÔÂ÷´Ü ±â´É¿Ü ½È¾îÇÏ´Â ¸ÞÀϸ¸ ¸·À» ¼ö ÀÖ´Â ±â´ÉÀÌ ÀÖÀ¸¸ç .. ¼ºÀÎ, ¼îÇÎ, CD, µ¿¿µ»ó µî... ¹Þ±â½ÈÀº ³»¿ëÀÌ µé¾î°£ °Í¸¸ °ÅºÎÇÒ ¼öµµ Àִµ¥ Á¶±Ý¸¸ ½Å°æ¾²¸é [±¤°í]¸ÞÀÏ °ÆÁ¤ ¶Ò...!! °£´ÜÇÏÁÒ...^ ^

¸¸¾à Á¦¸ñ¿¡ [±¤°í]¶ó´Â ¹®±¸°¡ ¾ø´Ù¸é º»¹®¿¡ "¼ö½Å°ÅºÎ"¶õ ¹®±¸¸¦ ÇÊÅ͸µÀ¸·Î Çغ¸¼¼¿ä ±×·³ ±¤°í¸ÞÀÏÀº ¸ø µé¾î¿À°í ÈÞÁöÅëÀ¸·Î »ç¶óÁý´Ï´Ù
 (Áï ±¤°í¸ÞÀÏÀº º»¹®¿¡ "¼ö½Å°ÅºÎ¸¦ ÇØÁÖ¼¼¿ä µî... Á˼ÛÇÕ´Ï´Ù µîÀÇ ¹®±¸°¡ ÀÖÀ¸´Ï ±× ¹®±¸¸¦ Æ÷ÇÔÇÑ °ÍÀº ¸ðµÎ ¸·¾Æ ÁÝ´Ï´Ù )

»õ·Î¿î µµ¸ÞÀÎ µî·Ï¾È³»...¹ÙÀÌ·¯½º °æ°í¾È³»...»õ·Î¿î ½Å»óÇ°À» ½Ñ °¡°Ý¿¡ ±¸ÀÔÇÒ ¼ö ÀÖ´Â ¼îÇθô...°ü±¤¾È³»...Çпø¾È³»...°¢Á¾Á¤º¸ ¼Ò½ÄÁö...¼ºÀÎ...µî...±× ¸ðµÎ¸¦ [±¤°í]¶ó°í ÇÏÁö¿ä~

±×¸®°í ¼ö½ÅÀÚµéÁß 60%°¡ ±¤°í¸ÞÀÏ¿¡ ÀÇÇØ ¼ö¸¹Àº Á¤º¸¸¦ ¾ò´Â´Ù°í ÇÕ´Ï´Ù, ¼ö¸¹Àº ±¤°íµé Áß ²À ±× Á¤º¸¸¦ ÇÊ¿ä·Î ÇÏ´Â ºÐµµ °è½Ã´Ù´Â »ç½Ç ¶§¹®¿¡ ±¤°í´Â Á¸ÀçÇÏ´Â °ÍÀÔ´Ï´Ù

±×¸®°í ÀÌ ¾î·Á¿î ½Ã´ë¿¡ »ì¾Æ³²±â À§ÇØ ¸öºÎ¸²Ä¡´Â ºÐµéÀ» À§ÇØ ÀÚ±âÁý ¹®´Ü¼ÓÀ» ÇÏ´ÂÀǹ̿¡¼­ [±¤°í] ÇÊÅ͸µ ¼±ÅÃÇϽÉÀÌ ¾î¶³·±Áö¿ä~~
±¤°íÁֵ鵵 ´õºÒ¾î »ì¾Æ°¡´Â »ç¶÷µéÀ̴ϱî¿ä

±¤°í¸¦ ÇÊ¿ä·Î ÇÏ´Â »ç¶÷¸¸ º¸±â¸¦ ¹Ù¶ó´Â ¸¶À½¿¡¼­....

¹«·á¼ºÀοµÈ­º¸±â

¹«·á¼ºÀθ¸È­º¸±â

 

  - ÃÖÈÄÀÇ Èñ¸ÁÀº ±àÁ¤ÀûÀÎ »ç°í¹æ½Ä ±×¸®°í »ç¶û... -

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 29 14:35:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f89.law9.hotmail.com [64.4.9.89]) by hub.freebsd.org (Postfix) with ESMTP id 8C7D237B416; Sat, 29 Dec 2001 14:35:46 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 29 Dec 2001 14:35:46 -0800 Received: from 24.9.137.53 by lw9fd.law9.hotmail.msn.com with HTTP; Sat, 29 Dec 2001 22:35:46 GMT X-Originating-IP: [24.9.137.53] From: "Chuck T." To: qa@freebsd.org, stable@freebsd.org Subject: 4.5-prerelease (27 dec) - UDMA33 ICRC error trashed fs Date: Sat, 29 Dec 2001 14:35:46 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 29 Dec 2001 22:35:46.0549 (UTC) FILETIME=[28799250:01C190B9] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I seem to have trashed my root file system on a 4.5-prerelease system cvsup'ed on 12/27. I'd installed 4.5-prerelease on a virgin (master) drive, and had been copying some configuration files from the 4.4-release (slave) drive. When I was copying the files I noticed a couple of UDMA ICRC errors before the kernel it fell back to PIO. I didn't notice any further problems until I moved the 4.4-release drive back to the master and tried to boot from it. The drive would not boot at all. I again reconfigured to boot from the 4.5 drive with the (thrashed) 4.4 drive as slave. Running fsck reported tons of errors (a log is available if needed). I've been running the same hardware with 4.4-release without problems since 4.4 was released. My system has two drive trays in a large tower case with a fairly long IDE cable (3 feet ?). I have not seen IDMA errors before, but I seldomly run with a slave drive. The logon messages and error messages are as follows: Dec 28 09:03:09 fastbsd /kernel: Copyright (c) 1992-2001 The FreeBSD Project. Dec 28 09:03:09 fastbsd /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Dec 28 09:03:09 fastbsd /kernel: The Regents of the University of California. All rights reserved. Dec 28 09:03:09 fastbsd /kernel: FreeBSD 4.5-PRERELEASE #1: Thu Dec 27 16:54:38 PST 2001 Dec 28 09:03:09 fastbsd /kernel: skip@fastbsd.pv1.ca.home.com:/usr/src/sys/compile/FASTBSD Dec 28 09:03:09 fastbsd /kernel: Timecounter "i8254" frequency 1193182 Hz Dec 28 09:03:09 fastbsd /kernel: Timecounter "TSC" frequency 851934846 Hz Dec 28 09:03:09 fastbsd /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (851.93-MHz 686-class CPU) Dec 28 09:03:09 fastbsd /kernel: Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Dec 28 09:03:09 fastbsd /kernel: Features=0x383f9ff Dec 28 09:03:09 fastbsd /kernel: real memory = 134205440 (131060K bytes) Dec 28 09:03:09 fastbsd /kernel: avail memory = 127176704 (124196K bytes) Dec 28 09:03:09 fastbsd /kernel: Preloaded elf kernel "kernel" at 0xc0373000. Dec 28 09:03:09 fastbsd /kernel: Pentium Pro MTRR support enabled Dec 28 09:03:09 fastbsd /kernel: Using $PIR table, 5 entries at 0xc00f0d10 Dec 28 09:03:09 fastbsd /kernel: npx0: on motherboard Dec 28 09:03:09 fastbsd /kernel: npx0: INT 16 interface Dec 28 09:03:09 fastbsd /kernel: pcib0: on motherboard Dec 28 09:03:09 fastbsd /kernel: pci0: on pcib0 Dec 28 09:03:09 fastbsd /kernel: pcib1: at device 1.0 on pci0 Dec 28 09:03:09 fastbsd /kernel: pci1: on pcib1 Dec 28 09:03:09 fastbsd /kernel: pci1: at 0.0 irq 5 Dec 28 09:03:09 fastbsd /kernel: isab0: at device 4.0 on pci0 Dec 28 09:03:09 fastbsd /kernel: isa0: on isab0 Dec 28 09:03:09 fastbsd /kernel: atapci0: port 0xb800-0xb80f at device 4.1 on pci0 Dec 28 09:03:09 fastbsd /kernel: ata0: at 0x1f0 irq 14 on atapci0 Dec 28 09:03:09 fastbsd /kernel: ata1: at 0x170 irq 15 on atapci0 Dec 28 09:03:09 fastbsd /kernel: uhci0: port 0xb400-0xb41f at device 4.2 on pci0 Dec 28 09:03:09 fastbsd /kernel: pci_cfgintr_search: linked (63) to configured irq 5 at 0:10:0 Dec 28 09:03:09 fastbsd /kernel: pci_cfgintr: 0:4 INTD routed to irq 5 Dec 28 09:03:09 fastbsd /kernel: usb0: on uhci0 Dec 28 09:03:09 fastbsd /kernel: usb0: USB revision 1.0 Dec 28 09:03:09 fastbsd /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Dec 28 09:03:09 fastbsd /kernel: uhub0: 2 ports with 2 removable, self powered Dec 28 09:03:09 fastbsd /kernel: chip1: port 0xe800-0xe80f at device 4.3 on pci0 Dec 28 09:03:09 fastbsd /kernel: xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xb000-0xb07f mem 0xe1800000-0xe180007f irq 5 at device 10.0 on pci0 Dec 28 09:03:09 fastbsd /kernel: xl0: Ethernet address: 00:50:04:a4:67:9e Dec 28 09:03:09 fastbsd /kernel: miibus0: on xl0 Dec 28 09:03:09 fastbsd /kernel: ukphy0: on miibus0 Dec 28 09:03:09 fastbsd /kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Dec 28 09:03:09 fastbsd /kernel: ahc0: port 0xa800-0xa8ff mem 0xe1000000-0xe1000fff irq 5 at device 11.0 on pci0 Dec 28 09:03:09 fastbsd /kernel: aic7850: Single Channel A, SCSI Id=7, 3/255 SCBs Dec 28 09:03:09 fastbsd /kernel: isa0: too many dependant configs (8) Dec 28 09:03:09 fastbsd /kernel: orm0: [±¤°í]¹®±¸°¡ µé¾î°£ ¸ÞÀÏÀ» 100% Â÷´ÜÇÏ´Â ¹æ¹ý !!

[±¤°í]¹®±¸°¡ µé¾î°£ ¸ÞÀÏÀ» 100% Â÷´ÜÇϴ¹ý !!

ÄÄÀ» ¾Ë°í³ª¸é ½ºÆÔ¸ÞÀÏ °ÆÁ¤¾ÈÇÏ°í ¾ó¸¶µçÁö ¸ÞÀÏÀ» ÀÌ¿ëÇÒ ¼ö°¡ ÀÖÁö¿©~

À¥¸ÞÀÏ ¸Þ´ºÁß È¯°æ¼³Á¤À̳ª¿É¼Ç¼±Åà - ÇÊÅͼ±ÅÃÈÄ - [±¤°í]¹®±¸¸¦ ¼ö½Å°ÅºÎ¿¡ Ãß°¡ÇÏ¸é ´ÙÀ½ºÎÅÍ Á¦¸ñ¿¡ [±¤°í]¶ó´Â ¹®±¸°¡ µé¾î°£ ¸ÞÀÏ°ú ¿µ¿øÈ÷ À̺°À» ÇÒ ¼ö ÀÖ´ä´Ï´Ù..^^    (¿åÀ» Çϰųª ½Å°í¸¸À¸·Ð ÀüÇô È¿°ú°¡ ¾øÀ½)

¸ðµç À¥¸ÞÀÏ¿¡´Â ½ºÆÔÂ÷´Ü ±â´É¿Ü ½È¾îÇÏ´Â ¸ÞÀϸ¸ ¸·À» ¼ö ÀÖ´Â ±â´ÉÀÌ ÀÖÀ¸¸ç .. ¼ºÀÎ, ¼îÇÎ, CD, µ¿¿µ»ó µî... ¹Þ±â½ÈÀº ³»¿ëÀÌ µé¾î°£ °Í¸¸ °ÅºÎÇÒ ¼öµµ Àִµ¥ Á¶±Ý¸¸ ½Å°æ¾²¸é [±¤°í]¸ÞÀÏ °ÆÁ¤ ¶Ò...!! °£´ÜÇÏÁÒ...^ ^

¸¸¾à Á¦¸ñ¿¡ [±¤°í]¶ó´Â ¹®±¸°¡ ¾ø´Ù¸é º»¹®¿¡ "¼ö½Å°ÅºÎ"¶õ ¹®±¸¸¦ ÇÊÅ͸µÀ¸·Î Çغ¸¼¼¿ä ±×·³ ±¤°í¸ÞÀÏÀº ¸ø µé¾î¿À°í ÈÞÁöÅëÀ¸·Î »ç¶óÁý´Ï´Ù
 (Áï ±¤°í¸ÞÀÏÀº º»¹®¿¡ "¼ö½Å°ÅºÎ¸¦ ÇØÁÖ¼¼¿ä µî... Á˼ÛÇÕ´Ï´Ù µîÀÇ ¹®±¸°¡ ÀÖÀ¸´Ï ±× ¹®±¸¸¦ Æ÷ÇÔÇÑ °ÍÀº ¸ðµÎ ¸·¾Æ ÁÝ´Ï´Ù )

»õ·Î¿î µµ¸ÞÀÎ µî·Ï¾È³»...¹ÙÀÌ·¯½º °æ°í¾È³»...»õ·Î¿î ½Å»óÇ°À» ½Ñ °¡°Ý¿¡ ±¸ÀÔÇÒ ¼ö ÀÖ´Â ¼îÇθô...°ü±¤¾È³»...Çпø¾È³»...°¢Á¾Á¤º¸ ¼Ò½ÄÁö...¼ºÀÎ...µî...±× ¸ðµÎ¸¦ [±¤°í]¶ó°í ÇÏÁö¿ä~

±×¸®°í ¼ö½ÅÀÚµéÁß 60%°¡ ±¤°í¸ÞÀÏ¿¡ ÀÇÇØ ¼ö¸¹Àº Á¤º¸¸¦ ¾ò´Â´Ù°í ÇÕ´Ï´Ù, ¼ö¸¹Àº ±¤°íµé Áß ²À ±× Á¤º¸¸¦ ÇÊ¿ä·Î ÇÏ´Â ºÐµµ °è½Ã´Ù´Â »ç½Ç ¶§¹®¿¡ ±¤°í´Â Á¸ÀçÇÏ´Â °ÍÀÔ´Ï´Ù

±×¸®°í ÀÌ ¾î·Á¿î ½Ã´ë¿¡ »ì¾Æ³²±â À§ÇØ ¸öºÎ¸²Ä¡´Â ºÐµéÀ» À§ÇØ ÀÚ±âÁý ¹®´Ü¼ÓÀ» ÇÏ´ÂÀǹ̿¡¼­ [±¤°í] ÇÊÅ͸µ ¼±ÅÃÇϽÉÀÌ ¾î¶³·±Áö¿ä~~
±¤°íÁֵ鵵 ´õºÒ¾î »ì¾Æ°¡´Â »ç¶÷µéÀ̴ϱî¿ä

±¤°í¸¦ ÇÊ¿ä·Î ÇÏ´Â »ç¶÷¸¸ º¸±â¸¦ ¹Ù¶ó´Â ¸¶À½¿¡¼­....

¹«·á¼ºÀοµÈ­º¸±â

¹«·á¼ºÀθ¸È­º¸±â

 

  - ÃÖÈÄÀÇ Èñ¸ÁÀº ±àÁ¤ÀûÀÎ »ç°í¹æ½Ä ±×¸®°í »ç¶û... -

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 29 16:19:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 2507537B41F; Sat, 29 Dec 2001 16:19:08 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id fBU0IjU16002; Sun, 30 Dec 2001 01:18:45 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200112300018.fBU0IjU16002@freebsd.dk> Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers In-Reply-To: <20011230002620.A630@tisys.org> To: Nils Holland Date: Sun, 30 Dec 2001 01:18:45 +0100 (CET) Cc: Matthew Dillon , Mike Silbersack , "Brandon S. Allbery KF8NH" , ian j hart , Matthew Gilbert , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Nils Holland wrote: > On Sat, Dec 29, 2001 at 10:42:20PM +0100, Søren Schmidt stood up and spoke: > > It seems Matthew Dillon wrote: > > > :Anyways could I have you guys read out all 256 PCI regs from the > > > :main chip that is the 0x03051106 one ? > > > : > > > :-Søren > > > > > > How is this done? > > > > With pciconf, fx: > > Is the 0x03051106 the KT133A? I guess so. Well, since I seem to have the > KT133 (without the A), I guess my values would be fairly useless... > However, if I'm wrong and the 0x03051106 *is* the KT133 that I have, I will > certainly post pciconf output! Its the KT133 with or without the A :) its the revid that tells them apart -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 29 16:54: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id CB16037B41A for ; Sat, 29 Dec 2001 16:54:00 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id D9462786E3; Sun, 30 Dec 2001 11:23:52 +1030 (CST) Date: Sun, 30 Dec 2001 11:23:52 +1030 From: Greg Lehey To: Juha Saarinen Cc: freebsd-stable@freebsd.org Subject: Re: VIA chip set "flaws" Message-ID: <20011230112352.F33871@monorchid.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, 30 December 2001 at 9:32:57 +1300, Juha Saarinen wrote: > http://www.theregister.co.uk/content/3/23502.html According to tecChannel Via has confirmed the problem, and says it is working on a solution. However it is not clear whether new drivers will be enough, or whether it will need a redesign of the chipsets. There is an unofficial patch produced by George Breese of Networking Resources available here, but as tecChannel says, you use this at your own risk That doesn't sound like hardware to me. Also, I've seen test results from sources I respect which show pretty much the opposite. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 29 17:23:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 2A3AB37B405; Sat, 29 Dec 2001 17:23:33 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id fBU1Nu654607; Sat, 29 Dec 2001 17:23:56 -0800 (PST) Date: Sat, 29 Dec 2001 17:23:56 -0800 (PST) From: Doug White To: "Chuck T." Cc: , Subject: Re: 4.5-prerelease (27 dec) - UDMA33 ICRC error trashed fs In-Reply-To: Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 29 Dec 2001, Chuck T. wrote: > I seem to have trashed my root file system on a 4.5-prerelease system > cvsup'ed on 12/27. I'd installed 4.5-prerelease on a virgin (master) drive, > and had been copying some configuration files from the 4.4-release (slave) > drive. When I was copying the files I noticed a couple of UDMA ICRC errors > before the kernel it fell back to PIO. I didn't notice any further problems > until I moved the 4.4-release drive back to the master and tried to boot > from it. The drive would not boot at all. I again reconfigured to boot from > the 4.5 drive with the (thrashed) 4.4 drive as slave. Running fsck reported > tons of errors (a log is available if needed). I seriously doubt this is a FreeBSD issue. Here's the relevant messages: > Dec 28 09:03:09 fastbsd /kernel: pcib0: bridge> on motherboard First, 440BX chipset, pretty standard fare. I've run hundreds of these boxes with IDE without problems. > Dec 28 09:03:09 fastbsd /kernel: ad0: 38166MB > [77545/16/63] at ata0-master UDMA33 > Dec 28 09:03:09 fastbsd /kernel: ad1: 6149MB [13328/15/63] at > ata0-slave UDMA33 > Dec 28 09:03:09 fastbsd /kernel: acd0: CDROM at > ata1-master using PIO4 Western Digital slaving a Western Digital. Plus a CDROM on the other channel. > Dec 28 09:22:11 fastbsd /kernel: ad1a: UDMA ICRC error reading fsbn 393471 > of 196704-196719 (ad1 bn 393471; cn 416 tn 5 sn 36) retrying > Dec 28 09:22:11 fastbsd /kernel: ad1a: hard error reading fsbn 393471 of > 196704-196719 (ad1 bn 393471; cn 416 tn 5 sn 36)ad1: DMA problem fallback to > PIO mode 'hard error' is generally Bad(tm). If it's been a while since you've power cycled this drive, it looks like it just went south on you. I would suggest downloading the Diagnostic toolset from Western Digital's site and scanning the drive for problems, and fixing them if possible. In any case your 4.4 install is probably garbage. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 29 17:36:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 294F437B417; Sat, 29 Dec 2001 17:36:21 -0800 (PST) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id fBU1aKd07260; Sat, 29 Dec 2001 17:36:20 -0800 (PST) Message-Id: <200112300136.fBU1aKd07260@ptavv.es.net> To: Greg Lehey Cc: Juha Saarinen , freebsd-stable@FreeBSD.ORG Subject: Re: VIA chip set "flaws" In-reply-to: Your message of "Sun, 30 Dec 2001 11:23:52 +1030." <20011230112352.F33871@monorchid.lemis.com> Date: Sat, 29 Dec 2001 17:36:20 -0800 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Sun, 30 Dec 2001 11:23:52 +1030 > From: Greg Lehey > Sender: owner-freebsd-stable@FreeBSD.ORG > > On Sunday, 30 December 2001 at 9:32:57 +1300, Juha Saarinen wrote: > > http://www.theregister.co.uk/content/3/23502.html > > According to tecChannel Via has confirmed the problem, and says it > is working on a solution. However it is not clear whether new > drivers will be enough, or whether it will need a redesign of the > chipsets. There is an unofficial patch produced by George Breese of > Networking Resources available here, but as tecChannel says, you use > this at your own risk > > That doesn't sound like hardware to me. Also, I've seen test results > from sources I respect which show pretty much the opposite. Greg, I'm a bit confused by your response. What part of this does not sound like hardware (all of it)? Test results show the opposite of what? R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 29 17:40:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 44EA337B417; Sat, 29 Dec 2001 17:40:38 -0800 (PST) Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.33 #1 (Red Hack)) id 16KUxp-0004XZ-00; Sun, 30 Dec 2001 14:40:37 +1300 Date: Sun, 30 Dec 2001 14:40:37 +1300 (New Zealand Daylight Time) From: Juha Saarinen To: Greg Lehey Cc: "freebsd-stable@freebsd.org" Subject: Re: VIA chip set "flaws" In-Reply-To: <20011230112352.F33871@monorchid.lemis.com> Message-ID: X-X-Sender: juha@vimfuego.saarinen.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 30 Dec 2001, Greg Lehey wrote: > That doesn't sound like hardware to me. Also, I've seen test results > from sources I respect which show pretty much the opposite. Well, http://www.tecchannel.de/hardware/817/3.html reckons it's because VIA chip sets only transfer 96 bytes per PCI burst unlike Intel's, which do 4096 bytes in a go. The following pages seem to indicate that you can program away this behaviour to a certain extent, but not fully. -- Juha Take off every sig! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 29 19:16:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from alg9469ey516l.bc.hsia.telus.net (alg9469ey516l.bc.hsia.telus.net [216.232.237.135]) by hub.freebsd.org (Postfix) with ESMTP id 2451437B41D for ; Sat, 29 Dec 2001 19:16:14 -0800 (PST) Received: (from darcy@localhost) by alg9469ey516l.bc.hsia.telus.net (8.11.5/8.11.4) id fBU5DGD00804; Sat, 29 Dec 2001 21:13:16 -0800 (PST) (envelope-from darcy) Content-Type: text/plain; charset="iso-8859-1" From: Darcy Buskermolen Organization: DBI Technologies To: sos@freebsd.dk, freebsd-stable@freebsd.org Subject: Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers Date: Sat, 29 Dec 2001 21:13:16 -0800 X-Mailer: KMail [version 1.2] References: <200112292142.fBTLgKE77526@freebsd.dk> In-Reply-To: <200112292142.fBTLgKE77526@freebsd.dk> MIME-Version: 1.0 Message-Id: <01122921131600.00401@alg9469ey516l> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here is the relevent info from my ASUS K7V which is exibiting this problem as well bash-2.04# pciconf -r -b pci0:0:0 0x0:0xff 0x00000006 0x00000011 0x00000091 0x00000006 0x00000006 0x00000000 0x00000010 0x00000022 0x00000002 0x00000000 0x00000000 0x00000006 0x00000000 0x00000000 0x00000000 0x00000000 0x00000008 0x00000000 0x00000000 0x000000e4 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000043 0x00000010 0x00000023 0x00000080 0x00000000 0x00000000 0x00000000 0x00000000 0x000000a0 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000017 0x000000a4 0x00000003 0x000000b4 0x0000004f 0x00000000 0x00000020 0x00000020 0x00000008 0x00000080 0x00000000 0x00000000 0x00000008 0x00000010 0x00000018 0x00000020 0x0000003c 0x000000ff 0x00000000 0x000000a0 0x000000a5 0x00000022 0x00000022 0x00000000 0x00000045 0x0000002c 0x00000065 0x0000002d 0x00000008 0x00000033 0x00000000 0x00000044 0x000000de 0x00000080 0x000000cc 0x0000000c 0x0000000e 0x00000081 0x000000d2 0x00000000 0x00000000 0x000000f4 0x00000001 0x00000002 0x00000000 0x00000000 0x00000000 0x00000000 0x0000000f 0x00000041 0x00000000 0x00000000 0x000000c0 0x00000000 0x00000000 0x00000000 0x00000002 0x00000000 0x00000000 0x00000000 0x0000009b 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000002 0x00000000 0x00000020 0x00000000 0x00000007 0x00000002 0x00000000 0x0000001f 0x00000000 0x00000000 0x00000000 0x00000000 0x0000006a 0x00000002 0x00000004 0x00000000 0x0000007f 0x00000066 0x00000082 0x000000a4 0x00000022 0x00000077 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000002 0x00000022 0x00000000 0x00000000 0x00000000 0x00000001 0x00000000 0x00000091 0x00000006 bash-2.04# dmesg Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-PRERELEASE #0: Sat Dec 29 14:53:32 PST 2001 root@alg9469ey516l:/usr/src/sys/compile/DBITECH Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 800032256 Hz CPU: AMD Athlon(tm) Processor (800.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 Features=0x183f9ff AMD Features=0xc0400000 real memory = 536788992 (524208K bytes) avail memory = 518057984 (505916K bytes) Preloaded elf kernel "kernel" at 0xc03bb000. ccd0-3: Concatenated disk drivers VESA: v2.0, 2048k memory, flags:0x0, mode table:0xc03474c2 (1000022) VESA: ATI MACH64 netsmb_dev: loaded Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00f15e0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: <3D Labs model 000a graphics accelerator> at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 9 at device 4.2 on pci0 uhci_run: setting run=0 uhci_run: done cmd=0x0 sts=0x20 uhci_run: setting run=1 uhci_run: done cmd=0x81 sts=0x0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 9 at device 4.3 on pci0 uhci_run: setting run=0 uhci_run: done cmd=0x0 sts=0x20 uhci_run: setting run=1 uhci_run: done cmd=0x81 sts=0x0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcm0: port 0xb000-0xb003,0xb400-0xb403,0xb800-0xb8ff irq 5 at device 4.5 on pci0 pci0: at 9.0 fxp0: port 0xa000-0xa01f mem 0xd8800000-0xd88fffff,0xdb000000-0xdb000fff irq 5 at device 10.0 on pci0 fxp0: Ethernet address 00:a0:c9:93:24:ec inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ed0: port 0x9800-0x981f irq 10 at device 11.0 on pci0 ed0: address 00:40:c7:29:67:4f, type NE2000 (16 bit) ed1: port 0x9400-0x941f irq 9 at device 13.0 on pci0 ed1: address 00:80:ad:00:3b:38, type NE2000 (16 bit) pcib1: on motherboard pci2: on pcib1 orm0: