Re: MCA: CPU 0 UNCOR PCC DTLB L1 error
Hi Guys, On Mon, May 16, 2011 at 09:51:23AM -0700, Jeremy Chadwick wrote: On Mon, May 16, 2011 at 06:23:19PM +0200, John Hay wrote: On Wed, May 11, 2011 at 05:26:50PM -0500, Alan Cox wrote: On Tue, May 10, 2011 at 7:52 AM, John Hay j...@meraka.org.za wrote: Hi, I have seen this panic a few times on a Gigabyte E350N-USB3 running 8-STABLE. I have only seen it while in X, but then the machine is always in X. At first, I just got these hangs, so bought a PCI-express RS232 card and could see these at last. For some reason it does not go past this, so I have not been able to get a dump yet. Have anybody an idea of why this is or how to debug it further? I searched the archives and found something similar about a year ago, but it looks like it was solved with a fix that got committed. http://www.freebsd.org/cgi/query-pr.cgi?pr=140338 I have now disabled mca in loader.conf with 'hw.mca.enabled=0' and I have not seen that panic again. I do occasionally see a panic in devfs_open(), but I guess that should be handled in another thread. The kernel is basically a GENERIC kernel with puc uncommented and the following in loader.conf vm.kmem_size=12G hw.mca.enabled=0 zfs_load=YES ahci_load=YES xhci_load=YES amdtemp_load=YES ng_ubt_load=YES uplcom_load=YES Here is the panic message and after that dmesg. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org MCA: Bank 0, Status 0xb6010015 MCA: Global Cap 0x0106, Status 0x0004 MCA: Vendor AuthenticAMD, ID 0x500f10, APIC ID 0 MCA: CPU 0 UNCOR PCC DTLB L1 error MCA: Address 0x8016c4000 Fatal trap 28: machine check trap while in user mode cpuid = 0; apic id = 00 instruction pointer = 0x43:0x80156af85 stack pointer = 0x3b:0x7fffcb18 frame pointer = 0x3b:0x80fe87800 code segment= base 0x0, limit 0xf, type 0x1b = DPL 3, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, IOPL = 0 current process = 2484 (initial thread) trap number = 28 panic: machine check trap cpuid = 0 KDB: stack backtrace: #0 0x80608d5e at kdb_backtrace+0x5e #1 0x805d6707 at panic+0x187 #2 0x808bf4c0 at trap_fatal+0x290 #3 0x808bfaa9 at trap+0x109 #4 0x808a7d94 at calltrap+0x8 Please try the following patch: Index: x86/x86/mca.c === --- x86/x86/mca.c (revision 219060) +++ x86/x86/mca.c (working copy) @@ -665,7 +665,8 @@ mca_setup(uint64_t mcg_cap) * for Erratum 383. */ if (cpu_vendor_id == CPU_VENDOR_AMD - CPUID_TO_FAMILY(cpu_id) == 0x10 amd10h_L1TP) + (CPUID_TO_FAMILY(cpu_id) == 0x10 || + CPUID_TO_FAMILY(cpu_id) == 0x14) amd10h_L1TP) workaround_erratum383 = 1; mtx_init(mca_lock, mca, NULL, MTX_SPIN); Index: i386/i386/pmap.c === --- i386/i386/pmap.c(revision 219060) +++ i386/i386/pmap.c(working copy) @@ -758,7 +758,8 @@ pmap_init(void) * machine monitor. */ if (vm_guest == VM_GUEST_VM cpu_vendor_id == CPU_VENDOR_AMD - CPUID_TO_FAMILY(cpu_id) == 0x10) + (CPUID_TO_FAMILY(cpu_id) == 0x10 || + CPUID_TO_FAMILY(cpu_id) == 0x14)) workaround_erratum383 = 1; /* Index: amd64/amd64/pmap.c === --- amd64/amd64/pmap.c (revision 219060) +++ amd64/amd64/pmap.c (working copy) @@ -727,7 +727,8 @@ pmap_init(void) * machine monitor. */ if (vm_guest == VM_GUEST_VM cpu_vendor_id == CPU_VENDOR_AMD - CPUID_TO_FAMILY(cpu_id) == 0x10) + (CPUID_TO_FAMILY(cpu_id) == 0x10 || + CPUID_TO_FAMILY(cpu_id) == 0x14)) workaround_erratum383 = 1; /* I have applied the patch, but got another one today. I still do not get a prompt or dump. :-( It just get stuck right after #4. If there is anything more that I can try, just ask. # MCA: Bank 0, Status 0xb6010015 MCA: Global Cap 0x0106, Status 0x0004 MCA: Vendor AuthenticAMD, ID 0x500f10, APIC ID 0 MCA: CPU 0 UNCOR PCC DTLB L1 error MCA: Address 0x808ace000 Fatal trap 28: machine check trap while
Re: MCA: CPU 0 UNCOR PCC DTLB L1 error
On Wed, May 11, 2011 at 05:26:50PM -0500, Alan Cox wrote: On Tue, May 10, 2011 at 7:52 AM, John Hay j...@meraka.org.za wrote: Hi, I have seen this panic a few times on a Gigabyte E350N-USB3 running 8-STABLE. I have only seen it while in X, but then the machine is always in X. At first, I just got these hangs, so bought a PCI-express RS232 card and could see these at last. For some reason it does not go past this, so I have not been able to get a dump yet. Have anybody an idea of why this is or how to debug it further? I searched the archives and found something similar about a year ago, but it looks like it was solved with a fix that got committed. http://www.freebsd.org/cgi/query-pr.cgi?pr=140338 I have now disabled mca in loader.conf with 'hw.mca.enabled=0' and I have not seen that panic again. I do occasionally see a panic in devfs_open(), but I guess that should be handled in another thread. The kernel is basically a GENERIC kernel with puc uncommented and the following in loader.conf vm.kmem_size=12G hw.mca.enabled=0 zfs_load=YES ahci_load=YES xhci_load=YES amdtemp_load=YES ng_ubt_load=YES uplcom_load=YES Here is the panic message and after that dmesg. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org MCA: Bank 0, Status 0xb6010015 MCA: Global Cap 0x0106, Status 0x0004 MCA: Vendor AuthenticAMD, ID 0x500f10, APIC ID 0 MCA: CPU 0 UNCOR PCC DTLB L1 error MCA: Address 0x8016c4000 Fatal trap 28: machine check trap while in user mode cpuid = 0; apic id = 00 instruction pointer = 0x43:0x80156af85 stack pointer = 0x3b:0x7fffcb18 frame pointer = 0x3b:0x80fe87800 code segment= base 0x0, limit 0xf, type 0x1b = DPL 3, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, IOPL = 0 current process = 2484 (initial thread) trap number = 28 panic: machine check trap cpuid = 0 KDB: stack backtrace: #0 0x80608d5e at kdb_backtrace+0x5e #1 0x805d6707 at panic+0x187 #2 0x808bf4c0 at trap_fatal+0x290 #3 0x808bfaa9 at trap+0x109 #4 0x808a7d94 at calltrap+0x8 Please try the following patch: Index: x86/x86/mca.c === --- x86/x86/mca.c (revision 219060) +++ x86/x86/mca.c (working copy) @@ -665,7 +665,8 @@ mca_setup(uint64_t mcg_cap) * for Erratum 383. */ if (cpu_vendor_id == CPU_VENDOR_AMD - CPUID_TO_FAMILY(cpu_id) == 0x10 amd10h_L1TP) + (CPUID_TO_FAMILY(cpu_id) == 0x10 || + CPUID_TO_FAMILY(cpu_id) == 0x14) amd10h_L1TP) workaround_erratum383 = 1; mtx_init(mca_lock, mca, NULL, MTX_SPIN); Index: i386/i386/pmap.c === --- i386/i386/pmap.c(revision 219060) +++ i386/i386/pmap.c(working copy) @@ -758,7 +758,8 @@ pmap_init(void) * machine monitor. */ if (vm_guest == VM_GUEST_VM cpu_vendor_id == CPU_VENDOR_AMD - CPUID_TO_FAMILY(cpu_id) == 0x10) + (CPUID_TO_FAMILY(cpu_id) == 0x10 || + CPUID_TO_FAMILY(cpu_id) == 0x14)) workaround_erratum383 = 1; /* Index: amd64/amd64/pmap.c === --- amd64/amd64/pmap.c (revision 219060) +++ amd64/amd64/pmap.c (working copy) @@ -727,7 +727,8 @@ pmap_init(void) * machine monitor. */ if (vm_guest == VM_GUEST_VM cpu_vendor_id == CPU_VENDOR_AMD - CPUID_TO_FAMILY(cpu_id) == 0x10) + (CPUID_TO_FAMILY(cpu_id) == 0x10 || + CPUID_TO_FAMILY(cpu_id) == 0x14)) workaround_erratum383 = 1; /* I have applied the patch, but got another one today. I still do not get a prompt or dump. :-( It just get stuck right after #4. If there is anything more that I can try, just ask. # MCA: Bank 0, Status 0xb6010015 MCA: Global Cap 0x0106, Status 0x0004 MCA: Vendor AuthenticAMD, ID 0x500f10, APIC ID 0 MCA: CPU 0 UNCOR PCC DTLB L1 error MCA: Address 0x808ace000 Fatal trap 28: machine check trap while in user mode cpuid = 1; apic id = 01 instruction pointer = 0x43:0x80af206d5 stack pointer = 0x3b:0x7fffb8e8 frame pointer = 0x3b:0x809b92450 code segment= base 0x0, limit 0xf, type 0x1b = DPL 3, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, IOPL = 0 current process = 8 (initial thread) trap number
Re: MCA: CPU 0 UNCOR PCC DTLB L1 error
On Mon, May 16, 2011 at 06:23:19PM +0200, John Hay wrote: On Wed, May 11, 2011 at 05:26:50PM -0500, Alan Cox wrote: On Tue, May 10, 2011 at 7:52 AM, John Hay j...@meraka.org.za wrote: Hi, I have seen this panic a few times on a Gigabyte E350N-USB3 running 8-STABLE. I have only seen it while in X, but then the machine is always in X. At first, I just got these hangs, so bought a PCI-express RS232 card and could see these at last. For some reason it does not go past this, so I have not been able to get a dump yet. Have anybody an idea of why this is or how to debug it further? I searched the archives and found something similar about a year ago, but it looks like it was solved with a fix that got committed. http://www.freebsd.org/cgi/query-pr.cgi?pr=140338 I have now disabled mca in loader.conf with 'hw.mca.enabled=0' and I have not seen that panic again. I do occasionally see a panic in devfs_open(), but I guess that should be handled in another thread. The kernel is basically a GENERIC kernel with puc uncommented and the following in loader.conf vm.kmem_size=12G hw.mca.enabled=0 zfs_load=YES ahci_load=YES xhci_load=YES amdtemp_load=YES ng_ubt_load=YES uplcom_load=YES Here is the panic message and after that dmesg. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org MCA: Bank 0, Status 0xb6010015 MCA: Global Cap 0x0106, Status 0x0004 MCA: Vendor AuthenticAMD, ID 0x500f10, APIC ID 0 MCA: CPU 0 UNCOR PCC DTLB L1 error MCA: Address 0x8016c4000 Fatal trap 28: machine check trap while in user mode cpuid = 0; apic id = 00 instruction pointer = 0x43:0x80156af85 stack pointer = 0x3b:0x7fffcb18 frame pointer = 0x3b:0x80fe87800 code segment= base 0x0, limit 0xf, type 0x1b = DPL 3, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, IOPL = 0 current process = 2484 (initial thread) trap number = 28 panic: machine check trap cpuid = 0 KDB: stack backtrace: #0 0x80608d5e at kdb_backtrace+0x5e #1 0x805d6707 at panic+0x187 #2 0x808bf4c0 at trap_fatal+0x290 #3 0x808bfaa9 at trap+0x109 #4 0x808a7d94 at calltrap+0x8 Please try the following patch: Index: x86/x86/mca.c === --- x86/x86/mca.c (revision 219060) +++ x86/x86/mca.c (working copy) @@ -665,7 +665,8 @@ mca_setup(uint64_t mcg_cap) * for Erratum 383. */ if (cpu_vendor_id == CPU_VENDOR_AMD - CPUID_TO_FAMILY(cpu_id) == 0x10 amd10h_L1TP) + (CPUID_TO_FAMILY(cpu_id) == 0x10 || + CPUID_TO_FAMILY(cpu_id) == 0x14) amd10h_L1TP) workaround_erratum383 = 1; mtx_init(mca_lock, mca, NULL, MTX_SPIN); Index: i386/i386/pmap.c === --- i386/i386/pmap.c(revision 219060) +++ i386/i386/pmap.c(working copy) @@ -758,7 +758,8 @@ pmap_init(void) * machine monitor. */ if (vm_guest == VM_GUEST_VM cpu_vendor_id == CPU_VENDOR_AMD - CPUID_TO_FAMILY(cpu_id) == 0x10) + (CPUID_TO_FAMILY(cpu_id) == 0x10 || + CPUID_TO_FAMILY(cpu_id) == 0x14)) workaround_erratum383 = 1; /* Index: amd64/amd64/pmap.c === --- amd64/amd64/pmap.c (revision 219060) +++ amd64/amd64/pmap.c (working copy) @@ -727,7 +727,8 @@ pmap_init(void) * machine monitor. */ if (vm_guest == VM_GUEST_VM cpu_vendor_id == CPU_VENDOR_AMD - CPUID_TO_FAMILY(cpu_id) == 0x10) + (CPUID_TO_FAMILY(cpu_id) == 0x10 || + CPUID_TO_FAMILY(cpu_id) == 0x14)) workaround_erratum383 = 1; /* I have applied the patch, but got another one today. I still do not get a prompt or dump. :-( It just get stuck right after #4. If there is anything more that I can try, just ask. # MCA: Bank 0, Status 0xb6010015 MCA: Global Cap 0x0106, Status 0x0004 MCA: Vendor AuthenticAMD, ID 0x500f10, APIC ID 0 MCA: CPU 0 UNCOR PCC DTLB L1 error MCA: Address 0x808ace000 Fatal trap 28: machine check trap while in user mode cpuid = 1; apic id = 01 instruction pointer = 0x43:0x80af206d5 stack pointer = 0x3b:0x7fffb8e8 frame pointer = 0x3b:0x809b92450 code segment = base 0x0, limit 0xf, type
MCA: CPU 0 UNCOR PCC DTLB L1 error
Hi, I have seen this panic a few times on a Gigabyte E350N-USB3 running 8-STABLE. I have only seen it while in X, but then the machine is always in X. At first, I just got these hangs, so bought a PCI-express RS232 card and could see these at last. For some reason it does not go past this, so I have not been able to get a dump yet. Have anybody an idea of why this is or how to debug it further? I searched the archives and found something similar about a year ago, but it looks like it was solved with a fix that got committed. http://www.freebsd.org/cgi/query-pr.cgi?pr=140338 I have now disabled mca in loader.conf with 'hw.mca.enabled=0' and I have not seen that panic again. I do occasionally see a panic in devfs_open(), but I guess that should be handled in another thread. The kernel is basically a GENERIC kernel with puc uncommented and the following in loader.conf vm.kmem_size=12G hw.mca.enabled=0 zfs_load=YES ahci_load=YES xhci_load=YES amdtemp_load=YES ng_ubt_load=YES uplcom_load=YES Here is the panic message and after that dmesg. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org MCA: Bank 0, Status 0xb6010015 MCA: Global Cap 0x0106, Status 0x0004 MCA: Vendor AuthenticAMD, ID 0x500f10, APIC ID 0 MCA: CPU 0 UNCOR PCC DTLB L1 error MCA: Address 0x8016c4000 Fatal trap 28: machine check trap while in user mode cpuid = 0; apic id = 00 instruction pointer = 0x43:0x80156af85 stack pointer = 0x3b:0x7fffcb18 frame pointer = 0x3b:0x80fe87800 code segment= base 0x0, limit 0xf, type 0x1b = DPL 3, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, IOPL = 0 current process = 2484 (initial thread) trap number = 28 panic: machine check trap cpuid = 0 KDB: stack backtrace: #0 0x80608d5e at kdb_backtrace+0x5e #1 0x805d6707 at panic+0x187 #2 0x808bf4c0 at trap_fatal+0x290 #3 0x808bfaa9 at trap+0x109 #4 0x808a7d94 at calltrap+0x8 Copyright (c) 1992-2011 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-STABLE #1: Fri Apr 29 10:14:26 SAST 2011 j...@angel.cids.org.za:/usr/obj/usr/src/sys/ANGEL amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD E-350 Processor (1600.07-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x500f10 Family = 14 Model = 1 Stepping = 0 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x802209SSE3,MON,SSSE3,CX16,POPCNT AMD Features=0x2e500800SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM AMD Features2=0x35ffLAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,IBS,SKINIT,WDT TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 7841800192 (7478 MB) ACPI APIC Table: GBTGBTUACPI FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: GBT GBTUACPI on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, cfcf (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0xf800-0xf8ff mem 0xd000-0xdfff,0xfdfc-0xfdff irq 18 at device 1.0 on pci0 pci0: multimedia, HDA at device 1.1 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16 at device 4.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: PCI-PCI bridge irq 16 at device 0.0 on pci1 pci2: PCI bus on pcib2 puc0: Sunix SER5437A port 0xef00-0xef1f,0xee00-0xee0f irq 16 at device 8.0 on pci2 puc0: [FILTER] uart0: 16950 or compatible on puc0 uart0: [FILTER] uart1: 16950 or compatible on puc0 uart1: [FILTER] ahci0: ATI IXP700 AHCI SATA controller port 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 0xfe02f000-0xfe02f3ff irq 19 at device 17.0 on pci0 ahci0: [ITHREAD] ahci0: AHCI v1.20 with 4 6Gbps ports, Port Multiplier supported ahcich0: AHCI channel at channel 0 on ahci0 ahcich0: [ITHREAD] ahcich1: AHCI channel at channel 1 on ahci0 ahcich1: [ITHREAD] ahcich2: AHCI channel at channel 2 on ahci0 ahcich2: [ITHREAD] ahcich3: AHCI channel at channel 3 on ahci0 ahcich3: [ITHREAD] ohci0: OHCI (generic) USB controller mem 0xfe02e000-0xfe02efff irq 18 at device 18.0 on pci0
autogenerated ipv6 addresses on vlans
::225:64ff:fef9:eb5d%ix0.3199 prefixlen 64 scopeid 0xd nd6 options=3PERFORMNUD,ACCEPT_RTADV media: Ethernet autoselect (10Gbase-SR full-duplex) status: active vlan: 3199 parent interface: ix0 ix2.1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:1b:21:57:ef:7c inet6 fe80::225:64ff:fef9:eb5d%ix2.1 prefixlen 64 scopeid 0xe nd6 options=3PERFORMNUD,ACCEPT_RTADV media: Ethernet autoselect (10Gbase-SR full-duplex) status: active vlan: 1 parent interface: ix2 ix2.8: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:1b:21:57:ef:7c inet6 fe80::225:64ff:fef9:eb5d%ix2.8 prefixlen 64 scopeid 0xf nd6 options=3PERFORMNUD,ACCEPT_RTADV media: Ethernet autoselect (10Gbase-SR full-duplex) status: active vlan: 8 parent interface: ix2 ## John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: zfs hang in zio-io_cv) with dd read
On Thu, Oct 07, 2010 at 09:28:22PM +0300, Andriy Gapon wrote: on 07/10/2010 20:31 John Hay said the following: Oct 7 17:11:49 thumper1 kernel: mvsch23: EMPTY CRPB 30 (-0) 0 4000 Can you rule out hardware (or driver-level) problems? E.g. by dd-ing to/from disk directly. Doing that in parallel on the same and/or different disks. Running any disk I/O benchmarks. Well, it might not be conclusive, but here is what I have done/tried: dd from a few select disks. They all do about 64MB/s and 900 interrupts per second. No kernel messages in dmesg or /var/log/messages. Typical command is: dd if=/dev/ada17 of=/dev/null bs=64k count=8 8 simultaneous dds from the 8 disks on a controller. I still get 64MB/s and 7000+ interrupts per second. No kernel messages. 6 simultaneous dds from a disk on each of the 6 controllers. I still get 64MB/s and 900+ interrupts per second per controller. No kernel messages. I made a small zfs raidz2 with 6 disks, one from each controller. dd to and from it with no problem. I made a small zfs raidz2 with 8 disks, all from one controller. dd to and from it at 190MB/s and 270MB/s, no problem. Bonnie++ finished without a problem. Next I made a zpool with 2 X raidz2 with 8 disks each. Each raidz2 on its own controller: zpool create -m none tst \ raidz2 ada0p1 ada1p1 ada2p1 ada3p1 ada4p1 ada5p1 ada6p1 ada7p1 \ raidz2 ada8p1 ada9p1 ada10p1 ada11p1 ada12p1 ada13p1 ada14p1 ada15p1 Creating a file with dd finished without a problem, about 245MB/s. # dd if=/dev/zero of=/export/tst.dd bs=64k count=16 16+0 records in 16+0 records out 1048576 bytes transferred in 42.732294 secs (245382567 bytes/sec) Reading from the file caused a hang again: # dd of=/dev/null if=/export/tst.dd bs=64k This message arrived in dmesg: mvsch15: EMPTY CRPB 13 (-14) 0 And a little later there was a lot more: mvsch15: Timeout on slot 1 mvsch15: iec 0200 sstat 0123 serr edma_s 1100 dma_c dma_s rs 0002 status 50 mvsch2: EMPTY CRPB 16 (-0) 2 4000 mvsch2: EMPTY CRPB 18 (-0) 1 4000 mvsch2: EMPTY CRPB 19 (-0) 2 4000 mvsch2: EMPTY CRPB 20 (-0) 3 4000 mvsch2: EMPTY CRPB 21 (-0) 0 4000 mvsch2: EMPTY CRPB 22 (-0) 1 4000 mvsch2: EMPTY CRPB 23 (-0) 2 4000 ... While this was happening, a dd from ada7p1 ran at normal speed, but from ada15p1 (which is on mvsch15) hanged for a while until there was a burst of mvsX interrupts and then finished without a further hickup. The original dd from tst.dd still have not finished. So it might be a driver problem, which only occur when pushed in a different than I could with my simultaneous dds to the raw partitions. If there are more tests that I can do, just say what. If someone wants a login to debug this, I can do it. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
zfs hang in zio-io_cv) with dd read
gptid/3c635efe-cc45-11df-b85d-00144f211378 N/A ad60p2 gptid/3c6eeb97-cc45-11df-b85d-00144f211378 N/A ad60p3 gptid/70eabeba-d067-11df-bc29-00144f211378 N/A ad62p1 gptid/7100fc20-d067-11df-bc29-00144f211378 N/A ad64p1 gptid/71165baa-d067-11df-bc29-00144f211378 N/A ad66p1 gptid/712f8225-d067-11df-bc29-00144f211378 N/A ad68p1 gptid/716a084d-d067-11df-bc29-00144f211378 N/A ad70p1 gptid/71853bf5-d067-11df-bc29-00144f211378 N/A ad72p1 gptid/719e0201-d067-11df-bc29-00144f211378 N/A ad74p1 gptid/71b74306-d067-11df-bc29-00144f211378 N/A ad76p1 gptid/71d1c11d-d067-11df-bc29-00144f211378 N/A ad78p1 gptid/71ea1b93-d067-11df-bc29-00144f211378 N/A ad80p1 gptid/7203c8d9-d067-11df-bc29-00144f211378 N/A ad82p1 gptid/721b5a67-d067-11df-bc29-00144f211378 N/A ad84p1 gptid/723a30d3-d067-11df-bc29-00144f211378 N/A ad86p1 gptid/7256a502-d067-11df-bc29-00144f211378 N/A ad88p1 gptid/72707600-d067-11df-bc29-00144f211378 N/A ad90p1 gptid/7289edd1-d067-11df-bc29-00144f211378 N/A ad92p1 gptid/72a21a0f-d067-11df-bc29-00144f211378 N/A ad94p1 gptid/72be2559-d067-11df-bc29-00144f211378 N/A ad96p1 gptid/72d70248-d067-11df-bc29-00144f211378 N/A ad98p1 ufsid/49a828ef1a6a2de8 N/A da0s1a ufs/flash1 N/A da0s1a ufsid/49a8c69e60e10953 N/A da0s2a ufs/flash2 N/A da0s2a ufsid/49b383f54383bf0d N/A da0s3a ufs/flash3 N/A da0s3a ufsid/49b383fca9c7233b N/A da0s4a ufs/flash4 N/A da0s4a thumper1# vmstat -i interrupt total rate irq17: ohci2 451815 98 irq18: ohci3 167391 36 irq19: ohci0 ohci1+ 137556 30 irq24: atapci0 19644 4 irq32: atapci1 15102 3 irq38: atapci3 19532 4 irq46: atapci4 23575 5 irq52: em0 452 0 irq53: em1 7582 1 irq61: em2 2319 0 irq62: em3 1427 0 irq68: atapci5 17632 3 irq76: atapci6 18112 3 cpu0: timer 9133048 1999 cpu1: timer 9126434 1998 cpu2: timer 9130320 1999 cpu3: timer 9130448 1999 Total 37402389 8189 John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: zfs hang in zio-io_cv) with dd read
On Thu, Oct 07, 2010 at 02:35:31PM +0200, Ivan Voras wrote: On 10/07/10 14:15, John Hay wrote: Hi, I got hold of a SunFire X4500 with 48 X 500G disks and thought to try FreeBSD 8-stable with zfs on it. I have setup the two boot disks in a zfs mirror and then the rest in a pool of 6 X raidz2 of 7 disks each. I have created a 10G file with dd in the second pool, but if I try to read it with dd, dd will hang in zio-io_cv) according to ^T. This happens everytime. The first time I saw messages about an interrupt storm, so I have put hw.intr_storm_threshold=1 in /etc/sysctl.conf. According to systat -vm 1 there is atapci for 2-3 seconds and then it is quiet. There are two things you could try: 1) use the AHCI driver (ahci_load=YES in /boot/loader.conf) and 2) disable superpages, they don't get along on a few models of Opterons (vm.pmap.pg_ps_enabled=0 in /boot/loader.conf). ahci does not grab them. According to the ahci man page, it can handle Marvell 88SX61xx, while these are MV88SX6081 according to pciconf -lcv: atap...@pci0:1:1:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit cap 07[60] = PCI-X 64-bit supports 133MHz, 512 burst read, 4 split transactions I have also set vm.pmap.pg_ps_enabled=0 in loader.conf, but that did not make a difference either. :-( Once dd hang in that zio-io_cv) state the rest of the machine is ok and everything works as long as you stay away from the directory where the file is that you dd from. There are no messages in dmesg or /var/log/messages. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: zfs hang in zio-io_cv) with dd read
On Thu, Oct 07, 2010 at 06:19:48PM +0200, Goran Lowkrantz wrote: --On October 7, 2010 17:50:42 +0200 John Hay j...@meraka.org.za wrote: On Thu, Oct 07, 2010 at 02:35:31PM +0200, Ivan Voras wrote: On 10/07/10 14:15, John Hay wrote: Hi, I got hold of a SunFire X4500 with 48 X 500G disks and thought to try FreeBSD 8-stable with zfs on it. I have setup the two boot disks in a zfs mirror and then the rest in a pool of 6 X raidz2 of 7 disks each. I have created a 10G file with dd in the second pool, but if I try to read it with dd, dd will hang in zio-io_cv) according to ^T. This happens everytime. The first time I saw messages about an interrupt storm, so I have put hw.intr_storm_threshold=1 in /etc/sysctl.conf. According to systat -vm 1 there is atapci for 2-3 seconds and then it is quiet. There are two things you could try: 1) use the AHCI driver (ahci_load=YES in /boot/loader.conf) and 2) disable superpages, they don't get along on a few models of Opterons (vm.pmap.pg_ps_enabled=0 in /boot/loader.conf). ahci does not grab them. According to the ahci man page, it can handle Marvell 88SX61xx, while these are MV88SX6081 according to pciconf -lcv: atap...@pci0:1:1:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit cap 07[60] = PCI-X 64-bit supports 133MHz, 512 burst read, 4 split transactions Then try mvs_load=YES m...@pci0:6:2:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI m...@pci0:5:1:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI That helped, thanks. Now the disks are detected as adaXX devices. The problem still happens though. I think it takes a little longer after I have started dd before it hangs, but it still hangs. One thing seems a little different though. Occasionaly a short burst of interrupts on the mvsX devices do come through. It also seems that a few seconds after I press ^T in the dd window, I see a burst of mvsX interrupts happen and dd will report in/out records and bytes. This did not happen with the ata driver. It is still hanging in zio-io_cv) though. I also see these messages in /var/log/messages Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 16 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 17 (-0) 1 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 18 (-0) 2 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 20 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 21 (-0) 1 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 22 (-0) 2 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 23 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 24 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 25 (-0) 1 4000 Oct 7 17:08:04 thumper1 kernel: Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 26 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 27 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 28 (-0) 1 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 29 (-0) 2 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 30 (-0) 3 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 31 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 2 (-18) 1 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 5 (-18) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 6 (-18) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 7 (-18) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 8 (-18) 1 4000 Oct 7 17:08:05 thumper1 kernel: Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 9 (-18) 2 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 10 (-18) 0 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 11 (-18) 1 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 12 (-18) 0 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 13 (-18) 0 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 14 (-18) 1 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 15 (-18) 2 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 16 (-18) 3 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 17 (-18) 0 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 18 (-22) 1 4000 Oct 7 17:08:05
Re: zfs hang in zio-io_cv) with dd read
On Thu, Oct 07, 2010 at 10:38:58AM -0700, Jeremy Chadwick wrote: On Thu, Oct 07, 2010 at 07:31:02PM +0200, John Hay wrote: On Thu, Oct 07, 2010 at 06:19:48PM +0200, Goran Lowkrantz wrote: --On October 7, 2010 17:50:42 +0200 John Hay j...@meraka.org.za wrote: On Thu, Oct 07, 2010 at 02:35:31PM +0200, Ivan Voras wrote: On 10/07/10 14:15, John Hay wrote: Hi, I got hold of a SunFire X4500 with 48 X 500G disks and thought to try FreeBSD 8-stable with zfs on it. I have setup the two boot disks in a zfs mirror and then the rest in a pool of 6 X raidz2 of 7 disks each. I have created a 10G file with dd in the second pool, but if I try to read it with dd, dd will hang in zio-io_cv) according to ^T. This happens everytime. The first time I saw messages about an interrupt storm, so I have put hw.intr_storm_threshold=1 in /etc/sysctl.conf. According to systat -vm 1 there is atapci for 2-3 seconds and then it is quiet. There are two things you could try: 1) use the AHCI driver (ahci_load=YES in /boot/loader.conf) and 2) disable superpages, they don't get along on a few models of Opterons (vm.pmap.pg_ps_enabled=0 in /boot/loader.conf). ahci does not grab them. According to the ahci man page, it can handle Marvell 88SX61xx, while these are MV88SX6081 according to pciconf -lcv: atap...@pci0:1:1:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit cap 07[60] = PCI-X 64-bit supports 133MHz, 512 burst read, 4 split transactions Then try mvs_load=YES m...@pci0:6:2:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI m...@pci0:5:1:0: class=0x01 card=0x11ab11ab chip=0x608111ab rev=0x09 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'MV88SX6081 8-port SATA II PCI-X Controller' class = mass storage subclass = SCSI That helped, thanks. Now the disks are detected as adaXX devices. The problem still happens though. I think it takes a little longer after I have started dd before it hangs, but it still hangs. One thing seems a little different though. Occasionaly a short burst of interrupts on the mvsX devices do come through. It also seems that a few seconds after I press ^T in the dd window, I see a burst of mvsX interrupts happen and dd will report in/out records and bytes. This did not happen with the ata driver. It is still hanging in zio-io_cv) though. I also see these messages in /var/log/messages Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 16 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 17 (-0) 1 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 18 (-0) 2 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 20 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 21 (-0) 1 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 22 (-0) 2 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 23 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 24 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 25 (-0) 1 4000 Oct 7 17:08:04 thumper1 kernel: Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 26 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 27 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 28 (-0) 1 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 29 (-0) 2 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 30 (-0) 3 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 31 (-0) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 2 (-18) 1 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 5 (-18) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 6 (-18) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 7 (-18) 0 4000 Oct 7 17:08:04 thumper1 kernel: mvsch31: EMPTY CRPB 8 (-18) 1 4000 Oct 7 17:08:05 thumper1 kernel: Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 9 (-18) 2 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 10 (-18) 0 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 11 (-18) 1 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 12 (-18) 0 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 13 (-18) 0 4000 Oct 7 17:08:05 thumper1 kernel: mvsch31: EMPTY CRPB 14
Re: csup in repomirror mode dumps core @ stable/8
On Thu, Sep 02, 2010 at 03:59:07AM +0400, Dmitry Morozovsky wrote: Dear colleagues, some 2 days ago my repo mirror (stable/8...@amd64) starts dumping core on copying repo: ... SetAttrs CVSROOT-src/Emptydir Edit CVSROOT-src/access,v Segmentation fault (core dumped) deleting files from sup/cvsroot-all/ did not help unfortunately, quick usual `make -DDEBUG_FLAGS=-g' in /usr/src/usr.bin/csup does not work, and I did not dig into this deeply yet, so trace are without parameters: (gdb) bt #0 0x00410676 in rcsdelta_addlog () #1 0x00412b15 in rcsparse_run () #2 0x00412453 in rcsfile_frompath () #3 0x00417c45 in updater_rcsedit () #4 0x00419a59 in updater_batch () #5 0x0041a1d1 in updater () #6 0x004158c4 in thread_start () #7 0x000800a1c511 in pthread_getprio () from /lib/libthr.so.3 #8 0x in ?? () Cannot access memory at address 0x7f1fa000 I see it here too on both a 7.2 and 8-stable machine. It looks like something in CVSROOT-src/access,v confuse it because moving that file away make the crash go away. I still have the old access,v if somebody is interested. A diff does not show anything wierd that I can see. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org --- /tmp/access,v-csup.crash2010-07-31 16:57:51.0 +0200 +++ /home/freebsd-cvs/CVSROOT-src/access,v 2010-08-30 22:31:11.0 +0200 @@ -1,10 +1,15 @@ -head 1.941; +head 1.942; access; symbols; locks; strict; comment@# @; +1.942 +date 2010.08.30.20.30.48;author rpaulo; state Exp; +branches; +next 1.941; + 1.941 date 2010.07.31.14.57.38;author philip; state Exp; branches; @@ -4715,11 +4720,13 @@ @@ -1.941 +1.942 log -...@svn rev 210685 on 2010-07-31 14:57:38Z by philip +...@svn rev 212009 on 2010-08-30 20:30:48Z by rpaulo -Take cbzimmer's commit bit into safekeeping per his request. +Please welcome Dimitry Andric (dim@@) as a src committer. Dimitry will be +work on Clang for now. +ed@@ is a co-mentor. Approved by: core @ @@ -4789,6 +4796,7 @@ des dfr dg +dim dougb dumbbell dwhite @@ -4972,6 +4980,19 @@ @ +1.941 +log +...@svn rev 210685 on 2010-07-31 14:57:38Z by philip + +Take cbzimmer's commit bit into safekeeping per his request. + +Approved by: core +@ +text +...@d66 1 +@ + + 1.940 log @SVN rev 210462 on 2010-07-25 10:06:56Z by philip ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
packet loss on ixgbe using vlans and routing. Was: packet loss on ixgbe using vlans and ipv6
Ok, after some more testing, I found that it was not only with ipv6 that I had packet loss. Routing either ipv4 or ipv6 had some loss. My test setup is the Dell T710 with its ix2 connected to a 10G port of a Nortel 4526GTX. On that port I have 2 vlans configured with half of the 1G ports in the one vlan and the other half in the other vlan. If I test with iperf from one of the machines on a 1G port to the T710, I get 920Mbit/s. If I do it simultaneously from a few machines connected to the 1G ports, all of them basically saturate their 1G links. If I now try to route from the one vlan to the other, ie. doing an iperf from a 1G connected machine, through the T710, to another 1G connected machine, I see packet loss, sometimes 100kbits/s. So it seems that as long as the T710 with the 10G card is the start or end point of the connection, I get no packet loss, but as soon as it has to route, something go wrong. John On Tue, Jul 20, 2010 at 06:20:39AM +0200, John Hay wrote: On Mon, Jul 19, 2010 at 01:46:18PM -0700, Jeremy Chadwick wrote: On Mon, Jul 19, 2010 at 10:25:42PM +0200, John Hay wrote: I have a Dell T710 with 4 X 10G ethernet interfaces (2 X Dual port Intel 82599 cards). It is running FreeBSD RELENG_8 last updated on July 13. What I see is packet loss (0 - 40%) on IPv6 packets in vlans, when the machine is not the originator of the packets. Let me try to describe a little more. If a neigbouring machine ping6 it, there will be packet loss. If it act as a router for ipv6, there will be packet loss. This happen even when the network is pretty idle and with different switches (Nortel and Cisco equipment). The packet loss is very fluctuating. Pinging 1000 packets might loose 1% one time and the next time 30%. Looking with tcpdump, I can see the packets arriving and going out, but the packet never arrive at the next machine. (My feeling is that they get lost inside the card.) The error counters on the switch does not increment. I do not see packet loss if the machine originate the packets, for example ping6 from the machine. Also ipv4 packets do not have any packets loss. If I do not use vlans, I don't see packet loss with ipv6 either. pciconf -l of the ethernet cards: i...@pci0:129:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:129:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:131:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:131:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 Can you provide pciconf -lvc output for the ix[0-3] cards instead? I believe Jack Vogel will need this. vmstat -i might also be helpful (full output). Ok, here is it and also a netstat -m thrown in. The numbers are pretty low because I rebooted after compiling a kernel with IPFIREWALL, ROUTETABLES, MROUTING and FLOWTABLE removed. I'll add my kernel config file with empty and commented out lines removed. After rebooting, I first tested with vlans (that is in my rc.conf) and then tested with the vlans unconfigured on ix2. i...@pci0:129:0:0:class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) i...@pci0:129:0:1:class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) i...@pci0:131:0:0:class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) i...@pci0:131:0:1:class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) output of vmstat
Re: packet loss on ixgbe using vlans and routing. Was: packet loss on ixgbe using vlans and ipv6
Ok, I found the culprit. If I do ifconfig ix2 -rxcsum the packet loss disappear. Still strange that it did not affect packets going to user-level. John On Wed, Jul 21, 2010 at 02:15:14PM +0200, John Hay wrote: Ok, after some more testing, I found that it was not only with ipv6 that I had packet loss. Routing either ipv4 or ipv6 had some loss. My test setup is the Dell T710 with its ix2 connected to a 10G port of a Nortel 4526GTX. On that port I have 2 vlans configured with half of the 1G ports in the one vlan and the other half in the other vlan. If I test with iperf from one of the machines on a 1G port to the T710, I get 920Mbit/s. If I do it simultaneously from a few machines connected to the 1G ports, all of them basically saturate their 1G links. If I now try to route from the one vlan to the other, ie. doing an iperf from a 1G connected machine, through the T710, to another 1G connected machine, I see packet loss, sometimes 100kbits/s. So it seems that as long as the T710 with the 10G card is the start or end point of the connection, I get no packet loss, but as soon as it has to route, something go wrong. John On Tue, Jul 20, 2010 at 06:20:39AM +0200, John Hay wrote: On Mon, Jul 19, 2010 at 01:46:18PM -0700, Jeremy Chadwick wrote: On Mon, Jul 19, 2010 at 10:25:42PM +0200, John Hay wrote: I have a Dell T710 with 4 X 10G ethernet interfaces (2 X Dual port Intel 82599 cards). It is running FreeBSD RELENG_8 last updated on July 13. What I see is packet loss (0 - 40%) on IPv6 packets in vlans, when the machine is not the originator of the packets. Let me try to describe a little more. If a neigbouring machine ping6 it, there will be packet loss. If it act as a router for ipv6, there will be packet loss. This happen even when the network is pretty idle and with different switches (Nortel and Cisco equipment). The packet loss is very fluctuating. Pinging 1000 packets might loose 1% one time and the next time 30%. Looking with tcpdump, I can see the packets arriving and going out, but the packet never arrive at the next machine. (My feeling is that they get lost inside the card.) The error counters on the switch does not increment. I do not see packet loss if the machine originate the packets, for example ping6 from the machine. Also ipv4 packets do not have any packets loss. If I do not use vlans, I don't see packet loss with ipv6 either. pciconf -l of the ethernet cards: i...@pci0:129:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:129:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:131:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:131:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 Can you provide pciconf -lvc output for the ix[0-3] cards instead? I believe Jack Vogel will need this. vmstat -i might also be helpful (full output). Ok, here is it and also a netstat -m thrown in. The numbers are pretty low because I rebooted after compiling a kernel with IPFIREWALL, ROUTETABLES, MROUTING and FLOWTABLE removed. I'll add my kernel config file with empty and commented out lines removed. After rebooting, I first tested with vlans (that is in my rc.conf) and then tested with the vlans unconfigured on ix2. i...@pci0:129:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) i...@pci0:129:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) i...@pci0:131:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) i...@pci0:131:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class
packet loss on ixgbe using vlans and ipv6
Hi, I have a Dell T710 with 4 X 10G ethernet interfaces (2 X Dual port Intel 82599 cards). It is running FreeBSD RELENG_8 last updated on July 13. What I see is packet loss (0 - 40%) on IPv6 packets in vlans, when the machine is not the originator of the packets. Let me try to describe a little more. If a neigbouring machine ping6 it, there will be packet loss. If it act as a router for ipv6, there will be packet loss. This happen even when the network is pretty idle and with different switches (Nortel and Cisco equipment). The packet loss is very fluctuating. Pinging 1000 packets might loose 1% one time and the next time 30%. Looking with tcpdump, I can see the packets arriving and going out, but the packet never arrive at the next machine. (My feeling is that they get lost inside the card.) The error counters on the switch does not increment. I do not see packet loss if the machine originate the packets, for example ping6 from the machine. Also ipv4 packets do not have any packets loss. If I do not use vlans, I don't see packet loss with ipv6 either. pciconf -l of the ethernet cards: i...@pci0:129:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:129:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:131:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:131:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 dmesg of the first ethernet card. The others look the same, except for the memory and irq values: ix0: Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.2.1 port 0xdcc 0-0xdcdf mem 0xd410-0xd417,0xd40f8000-0xd40fbfff irq 64 at device 0.0 on pci129 ix0: Using MSIX interrupts with 17 vectors ix0: [ITHREAD] ... ix0: Ethernet address: 00:1b:21:57:b4:20 ix0: PCI Express Bus: Speed 5.0Gb/s Width x8 If anybody need more info, please ask. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: packet loss on ixgbe using vlans and ipv6
On Mon, Jul 19, 2010 at 01:46:18PM -0700, Jeremy Chadwick wrote: On Mon, Jul 19, 2010 at 10:25:42PM +0200, John Hay wrote: I have a Dell T710 with 4 X 10G ethernet interfaces (2 X Dual port Intel 82599 cards). It is running FreeBSD RELENG_8 last updated on July 13. What I see is packet loss (0 - 40%) on IPv6 packets in vlans, when the machine is not the originator of the packets. Let me try to describe a little more. If a neigbouring machine ping6 it, there will be packet loss. If it act as a router for ipv6, there will be packet loss. This happen even when the network is pretty idle and with different switches (Nortel and Cisco equipment). The packet loss is very fluctuating. Pinging 1000 packets might loose 1% one time and the next time 30%. Looking with tcpdump, I can see the packets arriving and going out, but the packet never arrive at the next machine. (My feeling is that they get lost inside the card.) The error counters on the switch does not increment. I do not see packet loss if the machine originate the packets, for example ping6 from the machine. Also ipv4 packets do not have any packets loss. If I do not use vlans, I don't see packet loss with ipv6 either. pciconf -l of the ethernet cards: i...@pci0:129:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:129:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:131:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 i...@pci0:131:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 Can you provide pciconf -lvc output for the ix[0-3] cards instead? I believe Jack Vogel will need this. vmstat -i might also be helpful (full output). Ok, here is it and also a netstat -m thrown in. The numbers are pretty low because I rebooted after compiling a kernel with IPFIREWALL, ROUTETABLES, MROUTING and FLOWTABLE removed. I'll add my kernel config file with empty and commented out lines removed. After rebooting, I first tested with vlans (that is in my rc.conf) and then tested with the vlans unconfigured on ix2. i...@pci0:129:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) i...@pci0:129:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) i...@pci0:131:0:0: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) i...@pci0:131:0:1: class=0x02 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 64 messages in map 0x20 enabled cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x8(x8) output of vmstat -i interrupt total rate irq19: ehci0 28371 0 irq21: uhci2 uhci4+ 48 0 irq23: atapci046 0 irq34: mpt0 146954 2 cpu0: timer112205297 1999 irq256: bce0 52063 0 irq257: bce1 1 0 irq258: bce2 1 0 irq259: bce3 1 0 irq260: ix0:que 0 142258 2 irq261: ix0:que 1 56464 1 irq262: ix0:que 2 56199 1 irq263: ix0:que 3 56198 1 irq264: ix0:que 4 66569 1 irq265: ix0:que 5 56148 1 irq266: ix0:que 6 56217 1 irq267: ix0:que 7 56311 1 irq268: ix0:que 8 56169 1 irq269: ix0:que 9 69485 1 irq270: ix0:que 10
Re: ntpd struggling to keep up - how to fix?
On Wed, Feb 17, 2010 at 08:03:22PM +0100, Torfinn Ingolfsen wrote: On Wed, 17 Feb 2010 19:49:27 +0100 Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: Unfortunately, it isn't enough to keep the machine in sync all the time. But it is better than HPET so I'll keep it. This thread is interesting: http://lkml.indiana.edu/hypermail/linux/kernel/0903.1/01356.html Is there a way in FreeBSD to perform adjustmenst like adjtimex? 'apropos adjtime' only gives me a system call, the man pages for hz(9) and hardclock(9) doesn't exist on 8.0-stable (or on 7.2-stable). You can set the timecounter frequency with sysctl. On my one time server I have these lines in /etc/sysctl.conf machdep.tsc_freq=132658584 kern.timecounter.hardware=TSC John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: atheros issues with releng_8
On Mon, Dec 21, 2009 at 10:32:40PM -0500, Dan Langille wrote: Zane C.B. wrote: With the GENERIC kernel on releng_8 and releng_8_0, I am having issues with the Atheros wireless on my laptop. Upon boot I am getting the message below. ath0: Atheros 5424/2424 irq 17 at device 0.0 on pci3 ath0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x). ath0: cannot map register space device_attach: ath0 attach returned 6 Any suggestions? It was working fine on releng_6. http://www.freebsddiary.org/wireless-8.php Been there, done that, documented it. The attach that fails happen long before wlan devices and user level ifconfigs. Maybe pciconf -lv will show something or maybe showing some of the pci space with pciconf -r will give an idea why the attach fails. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Not getting an IPv6 in a jail
On Tue, Sep 01, 2009 at 09:30:15PM +0200, Major Domo wrote: Hello list, Apologies if this has been discussed already but I searched the web and the mailing lists and haven't found hints on my problem. I've got a jail, I assign it a set of IP addresses, and it just won't take the IP6 I give it. Uname: FreeBSD 7.2-STABLE Sysctl jail MIBs: security.jail.jail_max_af_ips: 255 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 0 security.jail.allow_raw_sockets: 1 security.jail.enforce_statfs: 2 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 0 /etc/rc.conf settings: jail_enable=YES jail_set_hostname_allow=NO jail_list=ns jail_ns_interface=lo252 jail_ns_hostname=[snip] jail_ns_ip=192.168.0.252,fe80::c0a8:fc jail_ns_rootdir=/var/jail/ns jail_ns_devfs_enable=YES jls -v: JID Hostname Path Name State CPUSetID IP Address(es) 23 [snip] /var/jail/ns ALIVE 2 192.168.0.252 fe80::c0a8:fc ifconfig lo252 from the host: lo252: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet 192.168.0.252 netmask 0x inet6 fe80::c0a8:fc%lo252 prefixlen 128 scopeid 0x5 ifconfig from the jail: re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC ether 00:e0:f4:19:e9:d2 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 pflog0: flags=141UP,RUNNING,PROMISC metric 0 mtu 33204 lo252: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet 192.168.0.252 netmask 0x ping6 from the host: PING6(56=40+8+8 bytes) fe80::c0a8:fc%lo252 -- fe80::c0a8:fc%lo252 16 bytes from fe80::c0a8:fc%lo252, icmp_seq=0 hlim=64 time=0.082 ms I fail to see what could be going wrong :( Any pointers please ? I have not used jails with link-local addresses, only global addresses and that works. It looks like you did not specify the whole link-local address in the jail_*_ip line. You need to add the %interface for a proper ipv6 link-local address, eg. fe80::c0a8:fc%lo252. Not everything works with link-local addresses though and jail might be one of them. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Not getting an IPv6 in a jail
On Tue, Sep 01, 2009 at 11:29:40PM +0200, FLEURIOT Damien wrote: On Tue, Sep 01, 2009 at 10:13:45PM +0200 or thereabouts, John Hay wrote: I have not used jails with link-local addresses, only global addresses and that works. It looks like you did not specify the whole link-local address in the jail_*_ip line. You need to add the %interface for a proper ipv6 link-local address, eg. fe80::c0a8:fc%lo252. Not everything works with link-local addresses though and jail might be one of them. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org Thanks for the hint John, I just tried by appending the interface % and it still won't work any better: rc.conf: jail_ns_ip=192.168.0.252,fe80::c0a8:fc%lo252 jls -v output doesn't change. ifconfig output within the jail doesn't change. ifconfig output on the host's lo252 doesn't change. I'm afraid I don't have spare IP6s to assign to my public interface so I can't test much more. You can use site-local (fec0::) or rfc4193 addresses for testing. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: fix ntptrace man page
On Tue, Aug 25, 2009 at 04:44:32PM +0200, Oliver Pinter wrote: On 8/25/09, Oliver Pinter oliver.p...@gmail.com wrote: funny, in /usr/src/usr.sbin/ntp/scripts/ntptrace implemented only the -n switch On 8/25/09, Gavin Atkinson gavin.atkin...@ury.york.ac.uk wrote: On Tue, 2009-08-25 at 04:58 +0200, Oliver Pinter wrote: Hi all! It's a small fix to ntpdate man page for freebsd 7-stable. I was looking at this a few days ago. The problem is not that the man page is wrong, it's that the man page documents an entirely different tool. For some reason, FreeBSD provides it's own version of ntptrace which lacks anything but the basic functionality, whereas the man page installed is that of the ntptrace tool as supplied in the ntpd distribution. It would seem much more sensible to use the official ntptrace and retain all the functionality people expoect from ntptrace, although I haven't yet found time to get to the bottom of why this was switched over from the official code in the first place. the ntpd code is under the contrib dir, but the ntptrace script is freebsds own script This is not true. The script comes with ntpd. The old version of ntptrace was replaced (in the ntpd tree) when ipv6 support was added. The reason was that the old version assumed that the refid field was an ip address. This was never part of the spec and was not true in a mixed ipv4/ipv6 setup. (Just because you use ipv4 to get to ntp server A, does not mean that it used ipv4 to sync from its upstream server.) The ntptrace html/man docs was just not updated. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ifconfig won't allow me to change ether address and inet address in the same command
On Tue, Oct 21, 2008 at 04:48:50PM -0200, Eduardo Meyer wrote: Hello :) Please, follow: # ifconfig rl0 ether 00:02:4f:0a:ce:f3 inet 192.168.2.12 netmask 255.255.255.0 ifconfig: can't set link-level netmask or broadcast # ifconfig rl0 inet 192.168.2.12 netmask 255.255.255.0 ether 00:02:4f:0a:ce:f3 ifconfig: ether: bad value # ifconfig rl0 inet 192.168.2.12 netmask 255.255.255.0 # ifconfig rl0 ether 00:02:4f:0a:ce:f3 I ask you some help, how can I accomplish both tasks with rc_ng? In /etc/rc.conf ifconfig_rl0=inet 192.168.2.12 netmask 255.255.255.0 ether 00:02:4f:0a:ce:f3 Won't allow me to do what I want. Any suggestions? I would like like to edit /etc/rc.local and any other kind of workaround. Can rc.conf issue ifconfig twice for the same nic? What about: ifconfig_rl0=ether 00:02:4f:0a:ce:f3 ipv4_addrs_rl0=192.168.2.12/24 John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random data corruption with USB mass storage on 7.0-BETA2
On Thu, Nov 15, 2007 at 09:52:34AM +0100, Heiko Wundram (Beenic) wrote: Hey all! While trying to upload some music to my mobile phone, I stumbled across the following odd behaviour when uploading files to an SD-card (inserted into my Sony Ericsson M600i) which is connected via USB as a mass-storage device: - ... umass0: Sony Ericsson Mobile Communications M600i, class 2/0, rev 2.00/0.00, addr 2 on uhub0 ... da0 at umass-sim0 bus 0 target 0 lun 0 da0: M600i 1.0 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 59MB (121821 512 byte sectors: 64H 32S/T 59C) ... - The card is formatted as FAT (by the phone software), and I can mount it with a plain mount -t msdosfs /dev/da0 /mnt without any kind of problems, except that directories that should be there, at least as displayed by the File Manager on the phone, aren't present under the mount point. There is no output to dmesg on the mounting (besides the GEOM label for the stick being removed). When copying files to the device, the phone displays that a transfer is taking place, and after finishing the transfer, comparing files on the mountpoint to the source files shows them as being equal. When I then unmount the device (which also runs cleanly, without any further output to dmesg except the reappearance of the GEOM label) and remount it, the copied files appear under the mount-point, but comparing the files on the mount-point against the source files shows them as being different. The sizes and modification dates are equal, though, and most of a file is correct, but non-deterministically every 16k or similar a stream of random bytes appears. When I do the same transfer from a 6.2-STABLE (last csupped some two months ago), the directories the phone reports appear under the mount-point, and the same transfer works properly (i.e., uploading the file, unmounting, remounting and comparing show the files as being the same, and playing the file on the phone works, and doesn't contain corruption artefacts). The 6.2-STABLE shows similar information on the device in dmesg (esp. the H/S/C info). 6.2-STABLE is a plain GENERIC kernel, with atapicam loaded (and some other device drivers for sound and Bluetooth), 7.0-BETA2 is a slightly adapted GENERIC (with SCHED_4BSD replaced with SCHED_ULE and SMP support removed) also with atapicam loaded (and some other device drivers for sound and bluetooth). I'll try to do some digging into the changes made to msdosfs between 6.2-STABLE and 7.0-BETA2 some time later on, but if anybody else is seeing this behaviour too or wants me to produce more debugging info on this (esp. some msdosfs debugging infos), feel free to send me a mail, and I'll try to get this done some time during the day. I'm not sure that it is msdosfs' fault. Last night I also corrupted my FAT based USB memory stick. But I used mtools and did not mount it. That was on 8-current though. I have not looked into it because there are other higher priority stuff also not working. :-/ John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Desired behaviour of ifconfig -alias
On Mon, Feb 12, 2007 at 11:59:40AM -0600, Brooks Davis wrote: On Mon, Feb 12, 2007 at 06:39:35PM +0100, Oliver Fromme wrote: Brooks Davis wrote: Oliver Fromme wrote: Jeremy Chadwick wrote: Oliver Fromme wrote: FWIW, I still use alias/-alias. Mainly because that's what has existed historically, and the term alias is what is used in reference to rc.conf ifconfig_iface_aliasX entries. Maybe it would make sense to remove alias from the rc.conf entries and simply number them. ipv4_addrs_interface is a much better replacement IMO. It's easy to use and doesn't required the hackish pseudo array traversal used by ifconfig_iface_aliasX. That might work for simple cases, but how do you specify other parameters beside the IPs if you need to? What do you need to set? It's sets IP and netmask. It doesn't handle broadcast, but I'd be pretty suprised if that's needed often. What else is needed? Axing ifconfig_iface_aliasX is not needed, but reducing the visiability of the interface in the documentation is probably in order particularly since it's quite fragile since you have to renumber whenever you remove an entry. Some stuff cannot be done on a single line, so I have abused the _aliasX mechanism for that. With the bridge interface: ifconfig_bridge0=ether 00:00:24:c0:0e:40 addm sis0 stp sis0 addm sis1 stp sis1 up ifconfig_bridge0_alias0=inet 146.64.84.1/24 Also with the atheros driver I had problems in the past with some parameters that did not like to be on a single commandline. FWIW I do not find the ifconfig iface -alias to be a problem... probably because I'm used to it. :-) What I do find silly is that you cannot do ifconfig iface tunnel inet6 inet6_addr inet6_addr anymore. It used to work and is still documented in ifconfig(8) to work. You have to swap inet6 and tunnel for it to work. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappearing IPv6 default route
-} else if (req == RTM_ADD SDL(gate)-sdl_alen == 0) {
+} else if (req == RTM_ADD SDL(gate)-sdl_alen == 0
+(rt-rt_flags RTF_HOST) != 0) {
ln-ln_state = ND6_LLINFO_INCOMPLETE;
Please do MFC. This patch seems to have solved all the problems I was
experiencing, and I can see the dancing Kame again now.
Cheers,
Matthew
Can you please try this patch too? The previous one I gave you, still
have some unwanted side effect. This one is by JINMEI, Tatuya and
seems to be without any... As far as I could test.
Thanks.
John
--
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
Index: nd6.c
===
RCS file: /home/ncvs/src/sys/netinet6/nd6.c,v
retrieving revision 1.48.2.14
diff -u -r1.48.2.14 nd6.c
--- nd6.c 20 Sep 2006 19:10:18 - 1.48.2.14
+++ nd6.c 2 Oct 2006 08:17:30 -
@@ -1315,7 +1315,7 @@
callout_init(ln-ln_timer_ch, 0);
/* this is required for ndp command. - shin */
- if (req == RTM_ADD) {
+ if (req == RTM_ADD (rt-rt_flags RTF_STATIC)) {
/*
* gate should have some valid AF_LINK entry,
* and ln-ln_expire should have some lifetime
@@ -1392,8 +1392,6 @@
ip6_sprintf(llsol), error));
}
}
- } else if (req == RTM_ADD SDL(gate)-sdl_alen == 0) {
- ln-ln_state = ND6_LLINFO_INCOMPLETE;
}
break;
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappearing IPv6 default route
On Sat, Sep 30, 2006 at 08:33:11PM +0100, Matthew Seaman wrote:
Dear list,
I've had IPv6 connectivity for some years via an IPv6 in IPv4 gif tunnel
courtesy of my ISP. However, about a week ago, when I upgraded to
6.2-PRERELEASE, I noticed it had mysteriously stopped working. (It may have
died before last week though; but that is the probable time) So this
weekend I set out to find out why.
It is a known problem that I caused. We are working on it. If you
want to, you can try this patch. It should fix your problem.
John
--
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
Index: sys/netinet6/nd6.c
===
RCS file: /home/ncvs/src/sys/netinet6/nd6.c,v
retrieving revision 1.67
retrieving revision 1.69
diff -I$FreeBSD: -u -r1.67 -r1.69
--- sys/netinet6/nd6.c 16 Sep 2006 06:24:28 - 1.67
+++ sys/netinet6/nd6.c 30 Sep 2006 20:25:33 - 1.69
@@ -1390,7 +1390,8 @@
ip6_sprintf(llsol), error));
}
}
- } else if (req == RTM_ADD SDL(gate)-sdl_alen == 0) {
+ } else if (req == RTM_ADD SDL(gate)-sdl_alen == 0
+ (rt-rt_flags RTF_HOST) != 0) {
ln-ln_state = ND6_LLINFO_INCOMPLETE;
}
break;
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Locking Issue
On Fri, Jun 30, 2006 at 01:03:09AM +0200, Michel Talon wrote: I guess I'm still just a bit stunned that a bug this obvious not only found it's way into the STABLE branch, but is still there. Maybe it's not as obvious as I think, or not many folks are using it? All I know for sure here is that if I had upgraded to 6.1 my network would have been crippled. Strange, since i upgraded to FreeBSD-6.1 and the NFS server to Fedora Core 5, my machine, NFS client is happy, and lockd works. It is first time since years i have no problem. It certainly did not work with FreeBSD-5 and i still have a machine with FreeBSD-6.0 which does not work properly (frequently loses the NFS mount, but it gets remounted some times later by amd). Anyways i have exactly 0 problem with the 6.1 machine. I could extend that to say that everything works very well on that machine, nothing is slow, including disk access. This has not always been the case. Stability wise, i have not seen any panic, hang or whatever since i have compiled a kernel adapted to my hardware. I got a panic with the generic kernel soon after installation, but now machine is totally stable. I only started to see the lockd problems when upgrading the server side to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x and 7-current and the lockd problem only showed up when upgrading the server from 5.x to 6.x. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rip2 ospf: freebsd 6.0
hi liste I'm looking for a dynamic routing (rip2, ospf) solution under freebsd 6.0. currently, I've always known zebra which exists in freebsd ports collection. do have a better idea? Though I haven't used it myself, I've talked to people who've done well with quagga for BGP. nice, i've had fun with one hour of gmake. It seems being supported by $M... let's see... thanks a lot for informations Quagga is a port and there is a package for it available, so you don't need to fight with gmake. I haven't used it with ospf yet, but have used it on IPv4 and IPv6 with rip1, rip2, ripng and bgp. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB keyboard support in 5.4
That did not *improve* things. It worked exactly the same. Experimenting, I put the 'device atkbd' line back in the kernel, having read that that makes the USB kb work as /dev/kbd0 instead of /dev/ukbd0, but that brought back the lockup behavior in single-user mode. Normal booting worked fine, OTT the 'busy' message, for both command-line and X. I'm just looking for perfection... ;-] I use: hint.atkbdc.0.disabled=1 hint.atkbd.0.disabled=1 in my /boot/device.hints file and then the keyboard works in single user mode. I guess the second one isn't needed. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ok, are all the panics fixed now?
So, I think we'll just include a warning with 4.9: WARNING! Do not attempt to stress a FreeBSD 4.9 machine if you: or Upgrade your FreeBSD to RedHat. s/RedHat/FreeBSD 4.8-RELEASE/ It's simple: we need to backout all these untested MFCs. Or fix the bugs. I don't know anything about the code in question, but now that people are getting repeatable panics, I assume that tracking down the bugs will be rather easier. There was a time when STABLE absolutely needed to be stable, but I'm not sure that's necessarily the case any more; now that we have all the release/security branches, I think it's safe to say that most systems which need absolute stability aren't going to be running STABLE. But the security branches don't get bug fixes, only security fixes. So at the the end we don't have a branch for stability anymore. I think that is a step in the wrong direction. I think by the time we get to x.4 or x.5 of a branch, it should be rock stable and only get bug fixes, with maybe device drivers added. Big changes should be avoided. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: r1.322 of src/Makefile.inc1
On Wed, Mar 05, 2003 at 12:07:01AM +0200, Ruslan Ermilov wrote: On Tue, Mar 04, 2003 at 04:50:37PM +, Ceri Davies wrote: Was this behaviour from mergemaster intended ? *** Displaying differences between ./etc/login.conf.db and installed version: Binary files /etc/login.conf.db and ./etc/login.conf.db differ Use 'd' to delete the temporary ./etc/login.conf.db Use 'i' to install the temporary ./etc/login.conf.db Use 'm' to merge the temporary and installed versions Use 'v' to view the diff results again Default is to leave the temporary file to deal with by hand How should I deal with this? [Leave it for later] d *** Deleting ./etc/login.conf.db Sorry, I don't use mergemaster(8) so I can't say. Doug was all for this change, so he may be of some help here. I think it is because previously login.conf.db was optional. Now it is kind of forced on you because all installations will have it. So either you have to remember to delete it or remember to update it after login.conf has changed. FWIW I never used login.conf.db on any of my machines because the system can read login.conf already and I don't maintain high login rate machines. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: r1.322 of src/Makefile.inc1
On Tue, Mar 04, 2003 at 10:35:39PM -0800, Doug Barton wrote: On Wed, 5 Mar 2003, John Hay wrote: On Wed, Mar 05, 2003 at 12:07:01AM +0200, Ruslan Ermilov wrote: On Tue, Mar 04, 2003 at 04:50:37PM +, Ceri Davies wrote: Was this behaviour from mergemaster intended ? *** Displaying differences between ./etc/login.conf.db and installed version: Binary files /etc/login.conf.db and ./etc/login.conf.db differ Use 'd' to delete the temporary ./etc/login.conf.db Use 'i' to install the temporary ./etc/login.conf.db Use 'm' to merge the temporary and installed versions Use 'v' to view the diff results again Default is to leave the temporary file to deal with by hand How should I deal with this? [Leave it for later] d *** Deleting ./etc/login.conf.db Sorry, I don't use mergemaster(8) so I can't say. Doug was all for this change, so he may be of some help here. I think it is because previously login.conf.db was optional. Now it is kind of forced on you because all installations will have it. So either you have to remember to delete it or remember to update it after login.conf has changed. Correct, but this is not a bad thing. :) mergemaster already prompts you to rebuild it when it's updated, so this is not rocket science. Well I did not mean it was necessarily bad, but it is a change and might be ok for -current. I'm just not so sure it is good for -stable too. Say for instance someone is used to just editing /etc/login.conf and have it take effect, so if he installs 4.8 and just edit /etc/login.conf, it won't take effect as it did before. FWIW I never used login.conf.db on any of my machines because the system can read login.conf already and I don't maintain high login rate machines. Are you sure that login time is the only time that this is read? :) Well, no. :-) John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: IPX tunnel through IP
I'm looking to bridge an IPX network at a remote location to the local IPX network, and the only method of communication is TCP/IP. Locally, I have a FreeBSD server, and I intend to use one at the remote location too. Looking in LINT, I see: options IPX #IPX/SPX communications protocols options IPXIP #IPX in IP encapsulation (not available) options IPTUNNEL#IP in IPX encapsulation (not available) Which implies that that's out of the picture. However, looking in usr/src/sys/netipx/ I see ipx_tun.c for encapsulating IP in IPX which is empty and marked not implemented, while ipx_ip.c for encapsulating IPX in IP seems to be fairly complete and nothing other than LINT saying it's not done. (this given that I am not even remotely familiar with the kernel or with IPX, so I'm probably way off here) Does anyone know about the status of this, or another method to do IPX through IP -- tun interfaces and generic tunnelling or anything? I can't seem to find enough info about this. IPXIP did work years ago. I used it between two FreeBSD boxes. I haven't used in ages though, so I don't know if it did rot with time. The not available next to it is probably a lie, because I was too lazy to document how to use it and so left that in to scare people off. :-) If you search in the mail archives, you should find how to configure it. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: D-Link DSB-R100 and the ufm driver
I just finished compiling ufm support into the kernel, and grabbed NetBSD's dsbr100 port to control my DSB-R100 device. With a little tweaking I got the port to compile, but when I run it I get inappropriate ioctl errors for USB_GET_DEVICEINFO and USB_DO_REQUEST. I think the device node may be wrong but here's what I have: crw-r--r-- 1 root operator 200, 0 Jun 25 00:55 /dev/ufm0 dmesg shows: ufm0: GemTek Corp USB FM Radio, rev 1.00/4.10, addr 2 I'm definitely not a USB guru, and need a bit of help getting this thing to work. The source is small enough, so it's attached. I haven't tried the NetBSD one, I am using the one from Warner's site: http://people.freebsd.org/~imp/ufmctl.c John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problem building stable
When trying to build the kernel I get the following error on make depend: rm -f .newdep make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | xargs mkdep -a -f .newdep -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/ipfilter -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/awi/awi_wicfg.c:89: i386/include/if_wavelan_ieee.h: No such file or directory mkdep: compile failed *** Error code 1 if_wavelan_ieee.h has moved. Try the patch attached. I'll commit it once it has survived my make release and if someone else hasn't done it before then. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] Index: sys/dev/awi/awi_wicfg.c === RCS file: /home/ncvs/src/sys/dev/awi/awi_wicfg.c,v retrieving revision 1.3.2.1 diff -u -r1.3.2.1 awi_wicfg.c --- sys/dev/awi/awi_wicfg.c 7 Dec 2000 04:09:39 - 1.3.2.1 +++ sys/dev/awi/awi_wicfg.c 18 Jun 2002 05:42:15 - @@ -86,7 +86,7 @@ #include dev/awi/am79c930var.h #undef _KERNEL /* XXX */ -#include i386/include/if_wavelan_ieee.h /* XXX */ +#include dev/wi/if_wavelan_ieee.h/* XXX */ #define_KERNEL /* XXX */ #include dev/awi/awireg.h #include dev/awi/awivar.h To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: kern/35660: LINT broken
LINT has been broken since 2002/03/07 17:48:57 when the puc device was added. Yes, I'll fix it tonight. It is just a small -current-ism that slipped in. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.4-RC2 is now available
I see that the X in the XF86336 directory is the same as what shipped in RC1. That, at least according to the file dates, are from the beginning of 2000. Is that on purpose? Couldn't we ship at least the X from the 4.3 release? John -- John Hay -- [EMAIL PROTECTED] ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.4-RC2/ ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/ 4.4rc2-install.iso (The ISO and package set are still mirroring but should be there soon). We have working GNOME 1.4 and KDE 2.2 packages on this release as well as a number of bug fixes since RC1. Please help us work out the final kinks so that we can ship a high-quality 4.4 release! Thanks, - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
ata timeouts after debug commits
Hi, I have been struggling with a Dell Latitude C800 here. FreeBSD 4.1 and 4.3 was working with no problems, but when I tried to upgrade it to 4-stable, it did not see the disk anymore. It just gave this message: # atapci0: Intel ICH2 ATA100 controller port 0xbfa0-0xbfaf at device 31.1 on pci 0 ata0: at 0x1f0 irq 14 on atapci0 ... ata0-master: ata_command: timeout waiting for intr ata0-master: identify failed # At the end I tracked it down to these commits: src/sys/i386/i386/db_trace.c,v 1.35.2.1 2001/07/12 02:57:11 bsd src/sys/i386/i386/support.s,v 1.67.2.4 2001/07/12 02:57:11 bsd src/sys/i386/include/cpufunc.h,v 1.96.2.2 2001/07/12 02:57:11 bsd If I back those commits out, the machine boots and see the disk with no problems. Anybody have any ideas about it? John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: cvs commit: src/release Makefile
On Thu, Sep 28, 2000 at 07:10:10PM +0900, Makoto MATSUSHITA wrote: But wait, wait a minute... If you wanna say "make release", you already know about that an exciting, cool, and misterious world is there. Why not adding vn_load="YES" to your loader.conf and reboot ? 1. No one has given an argument about what is so wrong about explicitly running kldload(8). And before someone says "just remember to run it before you type `make release'", then I'll argue why even have a release Makefile when one could just type all the commands in by hand. Hmmm. I have the vn device in the kernel that I use to build releases. Now (at least on -current where I have just tried it) I will end up with 2 vn's in the kernel. Won't that cause harm? -- beast:/home/cvsup # kldload vn.ko beast:/home/cvsup # kldstat -v Id Refs AddressSize Name 14 0xc010 20c00c kernel Contains modules: Id Name 1 cam 2 pci/ahc 3 miibus/amphy 4 miibus/brgphy 5 miibus/dcphy 6 miibus/xlphy 7 miibus/mlphy 8 miibus/nsphy 9 miibus/pnphy 10 miibus/pnaphy 11 miibus/rlphy 12 miibus/tlphy 13 miibus/ukphy 14 miibus/xmphy 15 nulldev 16 ppbus/lpt 17 ppc/ppbus 18 ppbus/ppi 19 random 20 pci/sym 21 vn 22 isab/isa 23 nexus/isa 24 isa/isahint 25 isa/pnp 26 aout 27 elf 28 shell 29 rootbus 30 procfs 31 if_loop 32 if_ppp 33 if_tun 34 pci/if_dc 35 dc/miibus 36 pci/if_de 37 pci/if_fxp 38 pci/if_xl 39 xl/miibus 40 pcib/pci 41 pci/pcib 42 pci/isab 43 pci/ign 44 ufs 45 mfs 46 scterm-sc 47 scrndr-vga 48 isa/pnpbios 49 mem 50 pci/piix 51 root/nexus 52 isa/sysresource 53 isa/attimer 54 isa/atpic 55 isa/atdma 56 nexus/npx 57 isa/npxisa 58 nexus/pcib 59 pci/hostb 60 isa/pcibus_pnp 61 atkbdc/atkbd 62 isa/atkbdc 63 isa/fdc 64 fdc/fd 65 isa/ppc 66 isa/sio 67 pci/sio 68 isa/sc 69 isa/vga 21 0xc0cb 3000 daemon_saver.ko Contains modules: Id Name 70 daemon_saver 31 0xc0ea3000 3000 vn.ko Contains modules: Id Name beast:/home/cvsup # ---------- John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SSH in 4.1 RELEASE for NonUS users
You have 2 options. If you have the crypto distribution with source, you
can go into /usr/src/secure/lib/librsaintl and build and install it. If
you don't want to build it, you can install the crypto distribution from
ftp.internat.freebsd.org, its crypto distibution was built with
USA_RESIDENT=NO and should give you librsaINTL* which is what is needed.
Doesn't one also need the following in make.conf:
MAKE_RSAINTL= YES # RSA (public key exchange)
The change was done earlier this month. Replaced RSAREF and was
WITH_RSAINTL until the 14th. Setting USA_RESIDENT=YES is only a part of
the check:
.if exists(${.CURDIR}/../../crypto/openssl/crypto/rsa/rsa_eay.c) \
(${USA_RESIDENT} != YES || defined(MAKE_RSAINTL))
SUBDIR+=librsaintl
.endif
No, you only need USA_RESIDENT=NO. It won't harm if you have MAKE_RSAINTL=YES,
but it isn't needed. MAKE_RSAINTL=YES is meant as a kind of override if
USA_RESIDENT=YES I think. Maybe the idea was to be able to build both.
John
--
John Hay -- [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
/modules/ empty in 4.x snaps
I see that the /modules directory is empty in the latest 4.x snaps. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How stable is the ATA code?
I heard some rumors about some instability on the new ATA code combined with DMA mode. Is this founded? Can I safely build the latest stable and have a peaceful sleep? From my experience the new ata driver isn't unstable. Where it works it generally works well. I have 2 machines where I have no problems with it. But like the rest of the PC world, there is no one true standard for things. So there are some chipsets or maybe versions of chipsets or maybe chipset and motherboard combinations where it has problems. In my case a no-name brand motherboard with a VIA 82C586 chipset. But these problems normally show up during instalation or just thereafter. If you didn't have problems during installation or just after that, you should be ok. Disabling DMA is not acceptable. I am running stable not current. :-) Hehehe. I think you can only demand these things if you pay for the development of the driver. :-) Something that I would really like to see is a way to disable DMA from the boot loader or some other place where it could be done early enough so that the install floppy can work. Maybe make hw.atamodes settable from the boot loader? I don't know how easy it will be, because I think the other sysctls that can be set from there only set a value, but setting hw.atamodes actually calls a function and I don't know if that can be done from the boot loader. Maybe an option in sysinstall? John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Anticipated release date for 3.4
At 10:21 AM 11/17/99 -0800, Jordan K. Hubbard wrote: Will be December 15th. The traditional code slush will go into effect on the 1st. November would be an excellent month for merging your changes, after which I'll be exercising my usual perogative of inspecting all potential changes with a more jaundiced eye. :) What happened to every 4 months? I think Jordan is just scared his build machine won't survive the Y2K rollover, so he wants to get 3.4 out of the door before then. :- John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP: ntpd users
This is just a heads up to ntpd users on 3.3-STABLE. 3.3-STABLE has been updated to draft-mogul-pps-api-05.txt, so ntp-4.0.98a and older will break on it because the old draft and the new one is quite incompatable. Does this have any relationship to the reason that the most recent xntpd sources don't compile on -current or -stable? On -stable cvsup'ed today I get: No, this is because of the nanokernel code by Dave Mills that we imported a while back. It has been this way for a while now. I just haven't had a good reason to bring it up yet. :-) In times past (2.2.8 was the most recent) I've never had any trouble compiling xntpd. Latest sources available at http://www.eecis.udel.edu/~ntp/. But if you look at them, you will see that the latest version of xntp3* is almost a year old. Their latest stuff is the ntp4 versions and that compiles just fine except for the heads up that I posted. If you really want to use xntp3, you can just ignore that error, because ntptime is only usefull for people experimenting with local clocks or you can use the one that comes with ntp4 which was fixed. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: [anoncvs.freebsd.org] Remote: Server does not permit empty password login.
I haven't used anonymous cvs to get FreeBSD, so I'm just guessing. Are you sure that FreeBSD make it available through ssh? None of the examples in the handbook suggests this. Try unsetting the CVS_RSH environment variable and see if it makes a difference. John -- John Hay -- [EMAIL PROTECTED] Dear administrators! anoncvs is still broken: |$ cvs -R up . |SSH Version 1.2.27 [i386--freebsd3.2], protocol version 1.5. |Standard version. Does not use RSAREF. |host: Reading configuration data /usr/local/etc/ssh_config |host: ssh_connect: getuid 1000 geteuid 1000 anon 1 |host: Connecting to anoncvs.freebsd.org [207.90.181.9] port 22. |host: Connection established. |host: Remote protocol version 1.99, remote software version 2.0.13 (non-commercial) |host: Waiting for server public key. |host: Received server public key (768 bits) and host key (1024 bits). |host: Host 'anoncvs.freebsd.org' is known and matches the host key. |host: Initializing random; seed file /home/laskavy/.ssh/random_seed |host: Encryption type: idea |host: Sent encrypted session key. |host: Installing crc compensation attack detector. |host: Received encrypted confirmation. |host: Remote: Server does not permit empty password login. --- |host: No agent. |host: Trying RSA authentication with key '[EMAIL PROTECTED]' |host: Remote: Bad file modes for /ctm/FreeBSD/anoncvs |host: Server refused our key. |host: Doing password authentication. |[EMAIL PROTECTED]'s password: |host: Remote: Server does not permit empty password login. --- |Permission denied. |cvs [update aborted]: end of file from server (consult above messages if any) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PPS Timing Interface and ONCORE GPS Clock / NTPD
You don't say which version of ntp you are using. If you are using something older than ntp-4.0.98b, please read the message I sent on Oct 16 to freebsd-stable with the subject line: HEADS UP: ntpd users If you are using ntp-4.0.98b or later tell me and I will look into it, because it is working for me. John -- John Hay -- [EMAIL PROTECTED] SUMMARY: ONCORE GPS Clock source for NTPD on FreeBSD was working with 3.3-Stable (Oct 8 1999). With 3.3-Stable (Nov 4 1999) NTPD fails with a 'time_pps_setparams: Inappropriate ioctl for device' message. It seems that '/dev/pps' may have been changed to '/dev/lppps0' REFERENCE: http://phk.freebsd.dk/ntp/ DISCUSSION: I had a GPS Clock working with FreeBSD 3.3-Stable as described at http://phk.freebsd.dk/ntp/ Using FreeBSD 3.3-Stable (as of Oct 8 1999) I had this working. NTPD would execute and diagnostic messages from the 'ONCORE' GPS receiver would appear on STDOUT. I recently upgraded to 3.3-Stable (Nov 4 1999). Now the NPTD program exits with a message: #ntpd -d -d some messages cut getnetnum given 127.127.30.0, got 127.127.30.0 (7f7f1e00) poll_update: at 0 127.127.30.0 poll 6 next 63 refclock_open: fd 8 modem status 7 refclock_ioctl: fd 8 flags 20 time_pps_setparams: Inappropriate ioctl for device So it seems that there is trouble with 'time_pps_setparams'. I checked 'dmesg' to see if the pps device appears: $dmesg | grep pps lppps0: Pulse per second Timing Interface on ppbus 0 This 'lppps0' device (3 p's) looks strange to me. I tried changing the name of /dev/pps to be /dev/lppps0 but to no avail. It seems that something may have changed in 3.3-Stable between Oct 8 and Nov 4 with respect to the pps device. Perhaps somebody can provide a pointer for me with respect to this problem. Marty Cawthon ChipChat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
