fxp lockups on 5.4-RC1
Hi. I was using a small test program to generate artificial network load on 5.4-RC1. The program sets up 1000 sockets that all connect, send a number of pipelined request, and then read the response from a nearby web server. After a short while the machine locked up, even the console was dead. Luckily DDB worked, so I was able to gather some backtraces (see below). Looks like something is stuck in the fxp process. Being a bit impatient, I did not check to see if the lockup would go away after some time. The problem went away after I increased nmbclusters to 32768. If more info is needed I can provide this of course. Cheers Michiel tr Tracing pid 23 tid 100017 td 0xc157da80 kdb_enter(c05d55bb) at kdb_enter+0x2b siointr1(c167f000) at siointr1+0xce siointr(c167f000) at siointr+0x38 intr_execute_handlers(c05ffac0,d4000bd8,0,c0c46460,c0c45240) at intr_execute_handlers+0x7d atpic_handle_intr(4) at atpic_handle_intr+0x96 Xatpic_intr4() at Xatpic_intr4+0x20 --- interrupt, eip = 0xc057ff87, esp = 0xd4000c1c, ebp = 0xd4000c28 --- uma_zfree_internal(c0c45240,c4173418,0,0,80) at uma_zfree_internal+0x153 bucket_free(c4173418,1,80,f3c8,c0c45bd8) at bucket_free+0x22 uma_zalloc_bucket(c0c45ba0,1) at uma_zalloc_bucket+0x263 uma_zalloc_arg(c0c45ba0,d4000c9c,1) at uma_zalloc_arg+0x274 fxp_add_rfabuf(c1616000,c16165d0) at fxp_add_rfabuf+0x2a fxp_intr_body(c1616000,c1616000,50,) at fxp_intr_body+0xd4 fxp_intr(c1616000) at fxp_intr+0xf4 ithread_loop(c1576800,d4000d48) at ithread_loop+0x151 fork_exit(c04838a0,c1576800,d4000d48) at fork_exit+0x74 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd4000d7c, ebp = 0 --- db ps pid proc uid ppid pgrp flag stat wmesgwchan cmd 375 c1731388 1001 370 375 0004002 [SLPQ zonelimit 0xc0c1f460][SLP] kqmaps 370 c1731c5c 1001 369 370 0004002 [SLPQ wait 0xc1731c5c][SLP] bash 369 c1731e200 1 369 0004102 [SLPQ wait 0xc1731e20][SLP] login 368 c18b50000 1 368 0004002 [SLPQ ttyin 0xc1574e10][SLP] getty 367 c18b51c40 1 367 0004002 [SLPQ ttyin 0xc1683010][SLP] getty 366 c18b53880 1 366 0004002 [SLPQ ttyin 0xc1683210][SLP] getty 365 c18b554c0 1 365 0004002 [SLPQ ttyin 0xc1683410][SLP] getty 364 c18b57100 1 364 0004002 [SLPQ ttyin 0xc1573010][SLP] getty 363 c18b58d40 1 363 0004002 [SLPQ ttyin 0xc1573210][SLP] getty 362 c172d54c0 1 362 0004002 [SLPQ ttyin 0xc1573410][SLP] getty 361 c172d7100 1 361 0004002 [SLPQ ttyin 0xc1573610][SLP] getty 321 c15c7e200 1 321 100 [SLPQ select 0xc060f364][SLP] sshd 199 c172d1c40 1 199 000 [SLPQ select 0xc060f364][SLP] devd 38 c172d8d40 0 0 204 [SLPQ - 0xd5445d18][SLP] schedcpu 37 c172da980 0 0 204 [SLPQ syncer 0xc060baec][SLP] syncer 36 c172dc5c0 0 0 204 [SLPQ vlruwt 0xc172dc5c][SLP] vnlru 35 c172de200 0 0 204 [SLPQ psleep 0xc060f84c][SLP] bufdaemon 9 c17310000 0 0 20c [SLPQ pgzero 0xc0616ed4][SLP] pagezero 8 c15b654c0 0 0 204 [SLPQ psleep 0xc0616f28][SLP] vmdaemon 7 c15b67100 0 0 204 [SLPQ psleep 0xc0616ee4][SLP] pagedaemon 34 c15b68d40 0 0 204 [IWAIT] swi0: sio 33 c15b6a980 0 0 204 [IWAIT] swi6: task queue 6 c15b6c5c0 0 0 204 [SLPQ - 0xc15e7e00][SLP] kqueue taskq 32 c15b6e200 0 0 204 [IWAIT] swi6:+ 5 c15c70000 0 0 204 [SLPQ - 0xc15f5000][SLP] thread taskq 31 c15c71c40 0 0 204 [IWAIT] swi6:+ 30 c15c73880 0 0 204 [SLPQ - 0xc0603a40][SLP] yarrow 4 c15c754c0 0 0 204 [SLPQ - 0xc0606428][SLP] g_down 3 c15c77100 0 0 204 [SLPQ - 0xc0606424][SLP] g_up 2 c15c78d40 0 0 204 [SLPQ - 0xc060641c][SLP] g_event 29 c15801c40 0 0 204 [IWAIT] swi1: net 28 c15803880 0 0 204 [IWAIT] swi4: vm 27 c158054c0 0 0 20c [RUNQ] swi5: clock sio 26 c15807100 0 0 204 [IWAIT] irq15: ata1 25 c15808d40 0 0 204 [IWAIT] irq14: ata0 24 c1580a980 0 0 204 [IWAIT] irq13: 23 c1580c5c0 0 0 204 [CPU 0] irq12: fxp0 22 c1580e200 0 0 204 [IWAIT] irq11: 21 c15b60000 0 0 204 [IWAIT] irq10: 20 c15b61c40 0 0 204 [IWAIT] irq9: 19 c15b63880 0 0 204 [IWAIT] irq8: rtc 18 c15780000 0 0 204 [IWAIT] irq7: 17 c15781c40 0 0 204 [IWAIT] irq6: 16 c15783880 0 0 204 [IWAIT] irq5: 15 c157854c0 0 0 204 [IWAIT] irq4: sio0 14 c15787100 0 0 204 [IWAIT] irq3: sio1 13 c15788d40 0 0 204 [IWAIT] irq1: atkbd0 12 c1578a980 0 0 204 [IWAIT] irq0: clk 11 c1578c5c0 0 0
UPDATE: ATA mkIII official patches for releng_5
I've just uploaded the latest ATA mkIII patches for releng_5 (and releng_5_4 for that matter). Since this work is now in -current there will only be releng_5 patches now and then if there is sufficient interest. Anyhow, they are on http:/people.freebsd.org/~sos/ATA Enjoy! -- -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi card recommendation
dear all, I would like to buy SCSI card which must: - support Ultra 320 - support RAID 0,1,5, and 1/0 any recommendation for FreeBSD-5.x ? Adaptec 7902 (I have an onboard one) works quite fine with asr(4) zero-channel raid card. It's a quite cheap solution but it performs stable and fast. Unfortunately asrutils aren't functional at least in 5.x (the specification/sources are available though, see archives). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Dell 2850 sporadically reboots (amd64)
Hi! We have a dual CPU Dell 2850 running fresh RELENG_5_4 (amd64). It reboots sporadically, a few times per day! It has a rather high load, running php, apache postfix. Is anyone else experiencing any problems with this kind of setup? diff against GENERIC kernel is minor: +# SMP +optionsSMP + +# SysV stuff +# This provides support for System V shared memory. +# +optionsSYSVSHM +optionsSYSVSEM +optionsSYSVMSG +optionsSHMMAXPGS=65536 +optionsSEMMNI=40 +optionsSEMMNS=240 +optionsSEMUME=40 +optionsSEMMNU=120 Also CPUTYPE?=nocona is set in /etc/make.conf Any ideas about this would ber *very* appreciated. Thanks! See also my previous post from yesterday. Regards, Palle $ dmesg Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RC2 #1: Wed Apr 13 01:24:15 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MELON Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.02-MHz K8-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x641dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,b14 AMD Features=0x2800SYSCALL,LM Hyperthreading: 2 logical CPUs real memory = 2147221504 (2047 MB) avail memory = 2061373440 (1965 MB) ACPI APIC Table: DELL PE BKC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 10 ioapic2: WARNING: intbase 64 != expected base 56 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 32-55 on motherboard ioapic2 Version 2.0 irqs 64-87 on motherboard acpi0: DELL PE BKC on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 amr0: LSILogic MegaRAID 1.51 mem 0xdfdc-0xdfdf,0xd80f-0xd80f irq 46 at device 14.0 on pci2 amr0: LSILogic PERC 4e/Di Firmware 513O, BIOS H418, 256MB RAM pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 4.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge at device 5.0 on pci0 pci5: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge at device 0.0 on pci5 pci6: ACPI PCI bus on pcib6 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xecc0-0xecff mem 0xdfae-0xdfaf irq 64 at device 7.0 on pci6 em0: Ethernet address: 00:11:43:37:a4:9e em0: Speed:N/A Duplex:N/A pcib7: ACPI PCI-PCI bridge at device 0.2 on pci5 pci7: ACPI PCI bus on pcib7 em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xdcc0-0xdcff mem 0xdf8e-0xdf8f irq 65 at device 8.0 on pci7 em1: Ethernet address: 00:11:43:37:a4:9f em1: Speed:N/A Duplex:N/A pcib8: ACPI PCI-PCI bridge at device 6.0 on pci0 pci8: ACPI PCI bus on pcib8 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xbce0-0xbcff irq 16 at device 29.0 on pci0 usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xbcc0-0xbcdf irq 19 at device 29.1 on pci0 usb1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0xbca0-0xbcbf irq 18 at device 29.2 on pci0 usb2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 29.7 (no driver attached) pcib9: ACPI PCI-PCI bridge at device 30.0 on pci0 pci9: ACPI PCI bus on pcib9 pci9: display, VGA at device 13.0 (no driver attached) isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 fdc0: floppy drive controller
Re: Dell 2850 sporadically reboots (amd64)
2005/4/13, Palle Girgensohn [EMAIL PROTECTED]: We have a dual CPU Dell 2850 running fresh RELENG_5_4 (amd64) CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.02-MHz K8-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 I am a little bit confused. amd64 with a dual xeon? -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell 2850 sporadically reboots (amd64)
We have a dual CPU Dell 2850 running fresh RELENG_5_4 (amd64). It reboots sporadically, a few times per day! It has a rather high load, running php, apache postfix. Is anyone else experiencing any problems with this kind of setup? I have a similar server which is not in production yet. So it hasn't been tested in a real world environment, but it does not reboot. CPUTYPE?=nocona is set in /etc/make.conf Have the same, looks fine. $ dmesg FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 You may want to disable HTT since the logical cpu may actually decrease the overall performance. See 'show stoppers' for the upcoming 5.4 release, there is an issue with 4 cpus and heavy on http://www.freebsd.org/releases/5.4R/todo.html. regards Claus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell 2850 sporadically reboots (amd64)
I am a little bit confused. amd64 with a dual xeon? Works fine. Pls. search the list before posting such replies. regards Claus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell 2850 sporadically reboots (amd64)
Cristiano Deana wrote: 2005/4/13, Palle Girgensohn [EMAIL PROTECTED]: We have a dual CPU Dell 2850 running fresh RELENG_5_4 (amd64) CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.02-MHz K8-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 I am a little bit confused. amd64 with a dual xeon? The FreeBSD amd64 supports Intel EM64T. See http://www.freebsd.org/platforms/amd64.html -- Uzi Klein B.M.B.Y Software Systems LTD. http://www.bmby.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
strangeness about netstat -m and mbuf clusters
Hi everybody, I have something real strange about netst -m in RELENG_5: caipi# uname -a FreeBSD caipi 5.4-STABLE FreeBSD 5.4-STABLE #11: Tue Apr 5 13:18:21 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/APP i386 caipi# netstat -m 463324 mbufs in use 4294964312/25600 mbuf clusters in use (current/max) 0/4/6656 sfbufs in use (current/peak/max) 109863 KBytes allocated to network 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 323 calls to protocol drain routines On all the machines where this happens I also see, that I cannot use vi to edit a file on an NFS filesystem. vi simply does nothing, it hangs and cannot be killed or only after a long time. Using truss is not possible: truss: PIOCBIS: Inappropriate ioctl for device (procfs is mounted). Using another editor (vim for example) works as expected. Any ideas, what I could test/do? Greetings, Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell 2850 sporadically reboots (amd64)
I am a little bit confused. amd64 with a dual xeon? Preseumably one of the newer 64 bit Xeons. I would home amd64 supports them doesnt it ? -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strangeness about netstat -m and mbuf clusters
On Wed, Apr 13, 2005 at 12:14:18PM +0200, Oliver Brandmueller wrote: Hi everybody, I have something real strange about netst -m in RELENG_5: caipi# uname -a FreeBSD caipi 5.4-STABLE FreeBSD 5.4-STABLE #11: Tue Apr 5 13:18:21 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/APP i386 caipi# netstat -m 463324 mbufs in use 4294964312/25600 mbuf clusters in use (current/max) 0/4/6656 sfbufs in use (current/peak/max) 109863 KBytes allocated to network 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 323 calls to protocol drain routines See the errata for 5.3, this is still true for later versions. On all the machines where this happens I also see, that I cannot use vi to edit a file on an NFS filesystem. vi simply does nothing, it hangs and cannot be killed or only after a long time. Using truss is not possible: truss: PIOCBIS: Inappropriate ioctl for device (procfs is mounted). Using another editor (vim for example) works as expected. Sounds like rpc.lockd is not set up on client and/or server. Kris pgp0B9SLHCGUs.pgp Description: PGP signature
Re: scsi card recommendation
dear all, I would like to buy SCSI card which must: - support Ultra 320 - support RAID 0,1,5, and 1/0 any recommendation for FreeBSD-5.x ? The Compaq SMART series have always worked well for me. Have a 3200 here on FreeBSD 5, and have tried almost all of them on FreeBSD 4 (from the old SMART 2 up to my current 5402). Nice cards in my opinion. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell 2850 sporadically reboots (amd64)
On Wed, 13 Apr 2005 19:28, Cristiano Deana wrote: 2005/4/13, Palle Girgensohn [EMAIL PROTECTED]: We have a dual CPU Dell 2850 running fresh RELENG_5_4 (amd64) CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.02-MHz K8-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 I am a little bit confused. amd64 with a dual xeon? EMT64... -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpWiV8Th0cpu.pgp Description: PGP signature
Re: strangeness about netstat -m and mbuf clusters
Hi Kris. On Wed, Apr 13, 2005 at 03:21:58AM -0700, Kris Kennaway wrote: See the errata for 5.3, this is still true for later versions. Err, OK, sorry. On all the machines where this happens I also see, that I cannot use vi to edit a file on an NFS filesystem. vi simply does nothing, it hangs and cannot be killed or only after a long time. Using truss is not possible: truss: PIOCBIS: Inappropriate ioctl for device (procfs is mounted). Using another editor (vim for example) works as expected. Sounds like rpc.lockd is not set up on client and/or server. rpc.lockd / rpc.statd were set up and were running on both client and server. And it had been working before. Well the actual problem was, that on the server the processes were still there, but the lockd didn't work anymore. After restarting the lockd there everything worked again. Thanx for the pointer! Now we start going for the rest of all the strange things :-) - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | pgpyiAuXlEtun.pgp Description: PGP signature
Re: [PATCH] puc/ppc and amd64
On Thu, 07 Apr 2005, David Taylor wrote: Hi, I've got an amd64 box with 1 built-in parallel port, which works fine. I also bought an add-on parallel port adapter card (a MosChip SemiConductors Nm9805 chip). After discovering puc, I enabled device puc and the card is now detected by puc, but doesn't appear to be picked up by the ppc driver. I have now, finally, figured out what was going on. After much wasted time trying to debug ppc_puc.c, I realised it wasn't even being compiled in the kernel. After adding dev/ppc/ppc_puc.c to files.amd64, everything worked a lot better. A patch (against 5-STABLE) is attached, which adds ppc_puc.c to all architectures with ppc.c listed (alpha, amd64, ia64 -- I can only test amd64, however). If this gets lost for ages, I'll add a PR... -- David Taylor --- sys/conf/files.alpha.oldWed Apr 13 12:20:57 2005 +++ sys/conf/files.alphaWed Apr 13 12:21:43 2005 @@ -183,6 +183,7 @@ dev/kbd/kbd.c optionalsc dev/kbd/kbd.c optionalukbd dev/ppc/ppc.c optionalppc +dev/ppc/ppc_puc.c optionalppc puc pci dev/sio/sio.c optionalsio dev/sio/sio_isa.c optionalsio isa dev/syscons/schistory.coptionalsc --- sys/conf/files.amd64.oldWed Apr 13 12:21:15 2005 +++ sys/conf/files.amd64Wed Apr 13 12:21:53 2005 @@ -133,6 +133,7 @@ dev/kbd/kbd.c optionalukbd dev/mem/memutil.c optionalmem dev/ppc/ppc.c optionalppc +dev/ppc/ppc_puc.c optionalppc puc pci dev/sio/sio.c optionalsio dev/sio/sio_isa.c optionalsio isa dev/syscons/apm/apm_saver.coptionalapm_saver apm --- sys/conf/files.ia64.old Wed Apr 13 12:21:05 2005 +++ sys/conf/files.ia64 Wed Apr 13 12:22:11 2005 @@ -59,6 +59,7 @@ dev/kbd/kbd.c optionalsc dev/kbd/kbd.c optionalukbd dev/ppc/ppc.c optionalppc isa +dev/ppc/ppc_puc.c optionalppc puc pci dev/syscons/schistory.coptionalsc dev/syscons/scmouse.c optionalsc dev/syscons/scterm-dumb.c optionalsc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] puc/ppc and amd64
On Wed, Apr 13, 2005 at 12:25:28PM +0100, David Taylor wrote: I have now, finally, figured out what was going on. After much wasted time trying to debug ppc_puc.c, I realised it wasn't even being compiled in the kernel. After adding dev/ppc/ppc_puc.c to files.amd64, everything worked a lot better. Yay. Does it work? I just added ID's to pucdata.c in my own branch to deal with the EasiDock 5000's onboard parallal port, but I thought parallel port puc wasn't known to work just now? BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UPDATE: ATA mkIII official patches for releng_5
Is there any plan to MFC this? -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.comMusings Of A Sentient Mind On Wed, Apr 13, 2005 at 10:07:21AM +0200, Søren Schmidt wrote: I've just uploaded the latest ATA mkIII patches for releng_5 (and releng_5_4 for that matter). Since this work is now in -current there will only be releng_5 patches now and then if there is sufficient interest. Anyhow, they are on http:/people.freebsd.org/~sos/ATA Enjoy! -- -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] %SPAMBLOCK-SYS: Matched [freebsd], message ok ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with NIC
This just started happing this evening not sure what is up. The nic is a Linksys LNE 100 V 4.something I forget now. I had some weird errors a while back when I first installed 5.3-RELEASE but i disabled ACPI and they seemed to work fine. Here is some info dc0: ADMtek AN985 10/100BaseTX port 0x1000-0x10ff mem 0xfc001000-0xfc0013ff irq 9 at device 12.0 on pci0on pci0 miibus0: MII bus on dc0i0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:03:6d:16:09:1e dc0: if_start running deferred for Giant dc0: [GIANT-LOCKED] This looks odd especaly this: Interrupt storm detected on irq9: dc0 ohci0; throttling interrupt source IP Filter: v3.4.35 initialized. Default = pass all, Logging = enabled dc0: TX underrun -- increasing TX thresholdn isa0 dc0: TX underrun -- increasing TX thresholdort 0x64,0x60 on isa0 dc0: failed to force tx and rx to idle stateed irqs 0 Interrupt storm detected on irq9: dc0 ohci0; throttling interrupt source : dc0: watchdog timeoutn't assign resources (port) dc0: failed to force tx and rx to idle stateort) dc0: watchdog timeoutn't assign resources (port) dc0: failed to force tx and rx to idle stateort) dc0: watchdog timeoutquency 379986358 Hz quality 800 dc0: failed to force tx and rx to idle state dc0: watchdog timeout4K020H1/A08.1500 [39560/16/63] at ata0-master UDMA66 dc0: failed to force tx and rx to idle state dc0: watchdog timeout Apr 13 05:21:16 www kernel: dc0: watchdog timeout Apr 13 05:21:16 www kernel: dc0: failed to force tx and rx to idle state Basicly I think I will replace this NIC cause I have had nothing but problems with it. It's an old one I have had in several boxs as a spare/backup. Might be going south on me. One other ? how do I start and stop networking on FreeBSD. I am just moving to FreeBSD from SV Linux and am used to a /etc/rc.d/init.d/network restart. Thanks for any input. -- Jaimie Garner Onsite PCS inc. 323 SE RIverside AV Grants Pass, OR 97526 541.471.1343 866.471.1343 [EMAIL PROTECTED] www.onistepcs.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi card recommendation
On Wed, 2005-04-13 at 09:58 +0700, Dikshie wrote: dear all, I would like to buy SCSI card which must: - support Ultra 320 - support RAID 0,1,5, and 1/0 any recommendation for FreeBSD-5.x ? thanks ! -dikshie- ___ We find the LSI MegaRaid 320-2x series works great (using it on a dual opteron system), especially with the battery-backed cache ... can be picked up for just under $1k Sven ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi card recommendation
Dikshie wrote: dear all, I would like to buy SCSI card which must: - support Ultra 320 - support RAID 0,1,5, and 1/0 any recommendation for FreeBSD-5.x ? I think the bigger question is Are there any SCSI RAID cards that can be fully monitored and managed from FreeBSD-5.x? Mike Lambert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with NIC
On Wed, Apr 13, 2005 at 05:50:27AM +, Jaimie Garner wrote: This just started happing this evening not sure what is up. The nic is a Linksys LNE 100 V 4.something I forget now. I had some weird errors a while back when I first installed 5.3-RELEASE but i disabled ACPI and they seemed to work fine. Here is some info dc0: ADMtek AN985 10/100BaseTX port 0x1000-0x10ff mem 0xfc001000-0xfc0013ff irq 9 at device 12.0 on pci0on pci0 miibus0: MII bus on dc0i0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:03:6d:16:09:1e dc0: if_start running deferred for Giant dc0: [GIANT-LOCKED] This looks odd especaly this: Interrupt storm detected on irq9: dc0 ohci0; throttling interrupt source Looks like the USB bus (ohci0) and your network card are sharing an interrupt line. My guess would be that a USB device generates too much interrupts causing the kernel to throttle them. This then screws up the network. According to polling(4), the dc driver supports polling instead of using an interrupt line. You could try rebuilding the kernel with polling support and see if the problem goes away. Or you could disable ohci0 in the bios, or plug the offending USB device into another port. Or you could try to force the dc triver to use another interrupt line. See the acpi manual page and google for 'irq routing freebsd'. I _think_ you should do the following: 'ps -xa|grep irq' will show which irq's are free. Let's say that irq 10 is still free. Now you'd have to find the pci address of the network card with 'pciconf -l -v|grep dc0'. Let's say you get something like '[EMAIL PROTECTED]:11:0' You can now tune the interrupt by setting the following in /boot/device.hints: hw.acpi.pci.link.0.11.0.irq=10 HTH, Roland -- R.F. Smith /\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \Respect for open standards pgpQNhMiujlSb.pgp Description: PGP signature
pxeboot
Hello, it was possible for me, to boot a bootable floppy-image over pxeboot. Is it possible to boot a CD-image over pxeboot? Please cc me your answers. Thank you all, Helmut __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi card recommendation
On Apr 12, 2005, at 11:32 PM, Vlad wrote: lsi logic's megaraid 320-2 works pretty good for me I'll second this recommendation. Vivek Khera, Ph.D. +1-301-869-4449 x806
Re: Problems with NIC
How about disable USB altogether since it is not used on this machine. Thanks for the info On Wednesday 13 April 2005 16:15, Roland Smith wrote: On Wed, Apr 13, 2005 at 05:50:27AM +, Jaimie Garner wrote: This just started happing this evening not sure what is up. The nic is a Linksys LNE 100 V 4.something I forget now. I had some weird errors a while back when I first installed 5.3-RELEASE but i disabled ACPI and they seemed to work fine. Here is some info dc0: ADMtek AN985 10/100BaseTX port 0x1000-0x10ff mem 0xfc001000-0xfc0013ff irq 9 at device 12.0 on pci0on pci0 miibus0: MII bus on dc0i0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:03:6d:16:09:1e dc0: if_start running deferred for Giant dc0: [GIANT-LOCKED] This looks odd especaly this: Interrupt storm detected on irq9: dc0 ohci0; throttling interrupt source Looks like the USB bus (ohci0) and your network card are sharing an interrupt line. My guess would be that a USB device generates too much interrupts causing the kernel to throttle them. This then screws up the network. According to polling(4), the dc driver supports polling instead of using an interrupt line. You could try rebuilding the kernel with polling support and see if the problem goes away. Or you could disable ohci0 in the bios, or plug the offending USB device into another port. Or you could try to force the dc triver to use another interrupt line. See the acpi manual page and google for 'irq routing freebsd'. I _think_ you should do the following: 'ps -xa|grep irq' will show which irq's are free. Let's say that irq 10 is still free. Now you'd have to find the pci address of the network card with 'pciconf -l -v|grep dc0'. Let's say you get something like '[EMAIL PROTECTED]:11:0' You can now tune the interrupt by setting the following in /boot/device.hints: hw.acpi.pci.link.0.11.0.irq=10 HTH, Roland -- Jaimie Garner Onsite PCS inc. 323 SE RIverside AV Grants Pass, OR 97526 541.471.1343 866.471.1343 [EMAIL PROTECTED] www.onistepcs.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UPDATE: ATA mkIII official patches for releng_5
Søren Schmidt [EMAIL PROTECTED] writes: I've just uploaded the latest ATA mkIII patches for releng_5 (and releng_5_4 for that matter). Seems to work fine on my laptop running 5.4-RC2. Suspend/resume doesn't work, but it didn't do that either with the code in RELENG_5_4. It seems to fail in a slightly different way now though. -- Christian Laursen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Mouse (moused) problems
Greetings to all: As the subject says, I am having a bit of problem with the mouse. I have been running FBSD 5.3 for about 2 weeks, X was working wonderfully, I even manage to get my ports upgraded using CTM, happiness was everywhere. Then came the moment to enable the sound system, I have an nforce chip. I went to /boot/kernel to see anything related to nforce but there was noting. Then, following the Handbook, I tried kldload snd_pcm but no sound still, tried kldload sbd_driver but still nothing. Tired of trying and reaching no positive results I went to bed, the next time I booted FBSD the mouse was gone. My /etc/rc.conf and /etc/X11/xorg.conf looks as follow: /etc/rc.conf # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=athena ifconfig_dc0=DHCP sshd_enable=YES usbd_enable=YES linux_enable=YES /etc/X11/xorg.conf Section InputDevice # Identifier and driver Identifier Mouse1 Driver mouse Option Protocol Auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 I ran /etc/rc.d/moused start and it gave no error message, not even an echo saying it was starting moused. Then I looked for sysmouse with: find / -name sysmouse -print but the only result I got was /dev/sysmouse (because it is supposed to be there); however, when I did an ls /dev sysmouse wasn't there, I tried ls -a but nothing. Any help regarding this will be appreciated. I was really having fun with FBSD until this little mouse incident and I don't want to redo the installation and upgrading of the ports. Have a nice day ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mouse (moused) problems
Didier Caamano wrote: the next time I booted FBSD the mouse was gone. In your rc.conf, there's no line like: moused_enable=YES You can run sysinstall, and go to mouse configuration and do there whatever is needed for your mouse. This procedure will add the appropriate lines into your rc.conf. Have a look at those lines and try to understand what was missing in your rc.conf. For sound support, see /usr/src/sys/conf/NOTES. It has a section on sound and what you need for specific sound cards. This may help. Good luck. Rob. __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel killing processes when out of swap
On Wed, Apr 13, 2005 at 12:07:11AM +0200, Matthias Buelow wrote: Nick Barnes [EMAIL PROTECTED] writes: This stuff has been discussed in the past. Indeed. For a couple of examples from the days before BSD systems got overcommit, see these threads from 1990 and 1991: http://groups-beta.google.com/group/comp.unix.aix/browse_frm/thread/91541dbf6 b658465/4c590978f1001507?q=overcommitrnum=14#4c590978f1001507 http://groups-beta.google.com/group/comp.unix.aix/browse_frm/thread/38c9bb999 6d30eb1/e8c30f78c44a3f62?q=overcommitrnum=12#e8c30f78c44a3f62 Apparently, it can be turned off on AIX, quoting from http://tinyurl.com/4epc8: ``If the PSALLOC environment variable is set to early, then every program started in that environment from that point on, but not including currently running processes, runs in the early allocation environment. In the early allocation environment, interfaces such as the malloc subroutine and the brk subroutine will fail if sufficient paging space cannot be reserved when the request is made. Processes run in the early allocation environment mode are not sent the SIGKILL signal if a low paging space condition occur.'' Googling showed that on Linux 2.6, overcommit can be disabled globally through the vm.overcommit_memory sysctl. I hope that some day some mechanism to solve that problem will be available in FreeBSD aswell. It's extremely disappointing that you can't turn this off. I've been bashing linux for months now about how they think it's OK to kill random processes. But at least they'll let you turn it off. -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828 Windows: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming, or what? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi card recommendation
Thank you all very much for your information. Vivek Khera ([EMAIL PROTECTED]) wrote: lsi logic's megaraid 320-2 works pretty good for me I'll second this recommendation. with best regards, -dikshie- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
