Perc 4e/di amr driver
Hi, Im installing 5.3 amd64 on Dell Poweredge servers 2800 and 2850. All machines have 4 to 8gb of ram and Perc 4e/di hardware Raid controller. The install does not boot completely because of the amr driver for the Perc 4e/di not recognising 4gb+. To solve this I specify hw.physmem=4G at boot time. The system then recognises 3.3gb of the ram. To solve the issue of the amr driver i took the driver source from 6.0-CURRENT kernel source, replacing the driver in the 5.3 kernel source with it and compiling a new kernel. This worked and now all system ram is recognised. My question is,as these servers will be production servers under a heavy load a lot of the time,will this new driver be stable enough to use or is it a risk. Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Peter Radcliffe wrote: Sren Schmidt [EMAIL PROTECTED] probably said: Well, you probably should take care of your sister first :) And no I dont have a paypal account, so far I've got by fine without it, by using other means as checks, wiretransfers etc etc... Do you have a list of things (particular devices or general categories) that would be useful for your work and an address ? :) Currently the most wanted list includes: SATA disks that supports NCQ and preferably also need 48bit addressing that is are bigger than 137G. Maxtors newest diamondmax 10 are a good bet here. SATA enclosures for hotswap support, Promise SuperSwap 4100 is a useable candidate as I can get docs on those. SATA ATAPI devices, CD/DVD drives/burners. Further down the line Port Multipliers etc, but we are not there yet.. The address I can give you in private mail if it gets that far -- -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Auto-Responder: E-mail address no longer in use
The email address [EMAIL PROTECTED] is no longer in use. To reach Jim McNally please resend your email to: [EMAIL PROTECTED] Support for DX-Ball 2, Tread Marks, Rival Ball Tournament and other games by Longbow Digital Arts is now located at: http://www.ldagames.com/support.html Thank you! Jim McNally, President Longbow Digital Arts www.LDAgames.com Original Message: Important! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hw.ata.ata_dma=0: can I do this during bootup at the loader prompt?
On Thu, 9 Dec 2004 19:31:40 +0100, Christian Lackas [EMAIL PROTECTED] wrote: * Scott Long [EMAIL PROTECTED] [041209 15:59]: Hello, It would be nice if I can set hw.ata.ata_dma=0 at the loader prompt during bootup, so that the system at least will boot from harddisk. Is that possible? Yes, that's possible. Drop the loader to the prompt and do the following: set hw.ata.ata_dma=0 boot btw: I have a similar problems, but not with the boot disc, but one of my data drives, thus I want ata_dma enabled for the other discs. I have to dispatch a atacontrol mode 1 foo UDMA33 to set this drive (slave on second controller) to UDMA33 (otherwise it would use UDMA100). But I have to do it before /etc/rc.d/fsck starts accessing the device. Right now I've added above line to the beginning of aforesaid script. Is there a nicer/better place to tell the kernel (don't like editing the rc-scripts). You can use /etc/rc.early for that. You'll have to create it if it doesn't yet exist. Put 'atacontrol mode 1 foo UDMA33' in it, and it should execute that command before mounting the drives. Best regards, Arjan Best regards Christian -- http://www.lackas.net/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Perc 4e/di amr driver
On Fri, 10 Dec 2004, L G wrote: Hi, Im installing 5.3 amd64 on Dell Poweredge servers 2800 and 2850. All machines have 4 to 8gb of ram and Perc 4e/di hardware Raid controller. The install does not boot completely because of the amr driver for the Perc 4e/di not recognising 4gb+. To solve this I specify hw.physmem=4G at boot time. The system then recognises 3.3gb of the ram. To solve the issue of the amr driver i took the driver source from 6.0-CURRENT kernel source, replacing the driver in the 5.3 kernel source with it and compiling a new kernel. This worked and now all system ram is recognised. My question is,as these servers will be production servers under a heavy load a lot of the time,will this new driver be stable enough to use or is it a risk. Thanks. The same changes that you grabbed from 6-CURRENT were made to 5-STABLE a few days ago, so you can just go ahead and update your whole system. 5.3-RELEASE has other bugs in 4GB handling that I've also fixed in 5-STABLE, and the AMR fixes rely on these fixes. But to answer your question, the driver is very stable under load now. Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Wiring down SCSI devices - was Re: Problem booting a Compaq Proliant 1600.
The information needed to wire down SCSI devices (which appears to be necesary in some cases with systems that have more than 1 SCSI controller) is contained in /usr/src/sys/i386/conf/NOTES for v4.10, and /sys/conf/NOTES for 5.3-STABLE Thanks to Scott Long for pointing out the latter. Mike Squires ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3: ed1: Ethernet address: aa:aa:aa:aa:aa:aa
I build a 5.3 kernel and source from source. When I booted, I got: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE-p2 #0: Fri Dec 10 22:48:56 GMT 2004 [EMAIL PROTECTED]:/home/obj/usr/src/sys/TIGERPROWL link_elf: symbol Debugger undefined KLD file acpi.ko - could not finalize loading Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) Origin = GenuineIntel Id = 0x652 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MM X,FXSR real memory = 268369920 (255 MB) avail memory = 257163264 (245 MB) npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX host to PCI bridge (AGP disabled) pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 5 Entries on motherboard pci0: PCI bus on pcib0 pci0: display, VGA at device 2.0 (no driver attached) cbb0: TI1131 PCI-CardBus Bridge irq 11 at device 3.0 on pci0 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: TI1131 PCI-CardBus Bridge irq 11 at device 3.1 on pci0 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0x860-0x86f,0x376,0x170-0x177,0x3f6,0x1f0-0x 1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xece0-0xecff irq 11 at device 7.2 o n pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82371AB/EB (PIIX4) USB controller 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 piix0: PIIX Timecounter port 0x840-0x84f at device 7.3 on pci0 Timecounter PIIX frequency 3579545 Hz quality 0 cpu0 on motherboard orm0: ISA Option ROM at iomem 0xc-0xcbfff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: Enhanced floppy controller at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0c01 can't assign resources (port) unknown: PNP0303 can't assign resources (port) unknown: PNP0f13 can't assign resources (irq) unknown: PNP0501 can't assign resources (port) unknown: PNP0401 can't assign resources (port) unknown: CSC can't assign resources (irq) unknown: PNP0700 can't assign resources (port) Timecounter TSC frequency 300684061 Hz quality 800 Timecounters tick every 10.000 msec ad0: 19077MB IBM-DJSA-220/JS4IAC1A [41344/15/63] at ata0-master UDMA33 acd0: CDRW UJDA310/1.38 at ata1-master PIO3 ed1: NETGEAR FA410TX at port 0x100-0x11f irq 11 function 0 config 32 on pccard0 ed1: [GIANT-LOCKED] ed1: Ethernet address: aa:aa:aa:aa:aa:aa ed1: if_start running deferred for Giant type NE1000 (8 bit) Mounting root from ufs:/dev/ad0s2a The problem is the GIANT-LOCKED ed1 section. An ethernet address of aa:aa:aa:aa:aa:aa is NOT a good thing. NOTE: I had not performed the MAKE INSTALLWORLD yet, this was a simple MAKE INSTALLKERNEL KERNCONF=TIGERPROWL; REBOOT sequence. Contrasted to the 5.2.1 kernel: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2.1-RELEASE #0: Wed Dec 8 19:44:50 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TIGERPROWL Preloaded elf kernel /boot/kernel/kernel at 0xc076. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) Origin = GenuineIntel Id = 0x652 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MM X,FXSR real memory = 268369920 (255 MB) avail memory = 255246336 (243 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 5 entries at 0xc00fb940 pcib0: Intel 82443BX
NFS firewalls
I'm trying to setup (ipfw) firewall on a server that exports home directories over NFS. Do I have to use nfsd_flafs and mountd_flags in rc.conf to specify ports on the server (advice I found in various mailing list archives) or is there a centralized solution? (what does nfs_reserved_port_only in rc.conf do?) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
netstat fails with memory allocation error and error in kvm_read
Hi We are trying to gather some debug information for a problem that is difficult to diagnose, as the machine always ends up hard frozen (does not do anything, can not break to debugger, does not respond to keyboard, etc.), so we are dumping output from netstat, vmstat, iostat etc. quite often. The cron jobs fail ever so often with error messages I do not quite understand, and I can not find anything relevant in the archives. Can anyone shed some light on this? Command:netstat -r Error message: netstat: kvm_read: Bad address Debug before: http://www.aub.dk/~jmp/fw/debug-2004.12.09-21.34.41.gz Debug after:http://www.aub.dk/~jmp/fw/debug-2004.12.09-21.35.06.gz # errors: 7 Command:netstat -an Error message: netstat: sysctl: net.inet.udp.pcblist: Cannot allocate memory Debug before: http://www.aub.dk/~jmp/fw/debug-2004.12.09-07.38.48.gz Debug after:http://www.aub.dk/~jmp/fw/debug-2004.12.09-07.39.04.gz # errors: 3 Command:netstat -an Error message: netstat: sysctl: net.inet.raw.pcblist: Cannot allocate memory Debug before: http://www.aub.dk/~jmp/fw/debug-2004.12.10-22.19.50.gz Debug after:http://www.aub.dk/~jmp/fw/debug-2004.12.10-22.20.10.gz # errors: 6 The number of errors are in the last five days. Kernelconfig (FIREWALL), dmesg, pf.conf etc. can be found at http://www.aub.dk/~jmp/fw/ The commands we are running are: netstat -i, netstat -m, netstat -s, netstat -an, netstat -r vmstat, vmstat -i, vmstat -f, vmstat -m, vmstat -z iostat ps waux every 15 seconds. We are running the same commands (plus pfctl -vvsa) from root's cron every minute. The hard lockups seems to be connected to our use of pf and altq, that is at least the problem we're trying to gather debug information for. Thanks in advance Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
