FreeBSD installation freeze! - FreeBSD doesn't like my hardware?
When installing freebsd (7.2, 8.0 betas, rc1, rc2, rc3 - AMD64) on a Clevo M540SR laptop (chipset VIA VN896), after menu option selection, the boot process freezes at Trying to mount root from ufs:/dev/md0. On verbose booting it freezes giving some mode information: md0: Preloaded image 4194304 bytes at 0x80c4be40 ATA PseudoRAID loaded flowtable cleaner started warning: no time-of-day clock registered, system time will not be set accurately Trying to mount root from ufs:/dev/md0 Start_init: trying /sbin/init Start_init: trying /sbin/oinit Start_init: trying /sbin/init.bak Start_init: trying /rescue/init Start_init: trying /stand/sysinstall I've tried already several boot hints (any of them with success) such as: apic.0.disabled = 1 sio.0.disasabled = 1 sio.1.disabled = 1 fdc.disabled = 1 kbdmux.0.disabled = 1 A possible solution I found over the internet would be to disable USB 2.0 support on bios, but bios options are very limited and won't allow me to do that. I can install FreeBSD 6.4 without any trouble and later upgrade to 7.0 went flawlessly, but upgrade to 7.2 brings up the freezes again on boot. ___ 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
AMD SR5690/SP5100 chipset
Hello! I wonder is there any support for AMD SR5690/SP5100 chipset in FreeBSD? -- SY, Marat ___ 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
NSIS compile failed on FreeBSD 7.2
I'm attempting to install NSIS (http://nsis.sourceforge.net/) on an
amd64 FreeBSD 7.2 system and having trouble. When I run
scons SKIPSTUBS=all SKIPPLUGINS=all SKIPUTILS=all SKIPMISC=all
NSIS_CONFIG_CONST_DATA_PATH=no
in the source directory for NSIS, I get a bunch of errors that look like:
/usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t'
('unsigned int') as first parameter
A google search gives me a link to this bug
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28582 that doesn't seem to
have been touched since 2006. Is there someway around this compile error?
Thanks,
Matt
___
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: NSIS compile failed on FreeBSD 7.2
On 2009-11-17 15:48, Matt Wilks wrote:
in the source directory for NSIS, I get a bunch of errors that look like:
/usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t'
('unsigned int') as first parameter
Does a .cpp file consisting of just the following:
#include new
compile on your system? If so, it is most likely something in the NSIS
headers that screws up either the definition of operator new, size_t, or
some other vital thing.
___
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: NSIS compile failed on FreeBSD 7.2
Matt Wilks wrote: I'm attempting to install NSIS (http://nsis.sourceforge.net/) on an amd64 FreeBSD 7.2 system and having trouble. When I run [snip] From the project's home page: NSIS (Nullsoft Scriptable Install System) is a professional open source system to create Windows installers. Is this supposed to compile on unix-like systems? Mikael ___ 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: NSIS compile failed on FreeBSD 7.2
On Tue, Nov 17, 2009 at 05:18:02PM +0100, Mikael Bak wrote: Matt Wilks wrote: I'm attempting to install NSIS (http://nsis.sourceforge.net/) on an amd64 FreeBSD 7.2 system and having trouble. When I run [snip] From the project's home page: NSIS (Nullsoft Scriptable Install System) is a professional open source system to create Windows installers. Is this supposed to compile on unix-like systems? Yes it is. It's supposed to be compilable on any POSIX-compliant system, without requiring WINE. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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: 8.0-rc2 dropped hardwaresupport
On Thu, 2009-11-12 at 13:07 -0500, Larry Baird wrote: Marten, I did some more testing, and I made an error on the ALIX 1C since it does boot but it hangs on devd but for WRAP 1C and 2E: PC Engines WRAP.2B/2C v1.11 640 KB Base Memory 130048 KB Extended Memory 01F0 Master 044A CF CARD 2GB Phys C/H/S 3909/16/63 Log C/H/S 977/64/63 1 FreeBSD 2 FreeBSD F6 PXE Boot: 1 Here it ends Would you recommend to downgrade the bios? I have version 1.11 on all boards. The 0.99h BIOS is for ALIX boards. I am running v1.11 on my WRAP boards. PC Engines WRAP.1C/1D/1E v1.11 640 KB Base Memory 130048 KB Extended Memory Looking at your geometry, I would recommend verifing that the BIOS is set for LBA mode (not CHS). If you change mode, you will probably need to reinstall FreeBSD. Thanks for your input, I seems NanoBSD specific, while I have been trying different disk geometrics and multiple cf-cards on NanoBSD I was not succesfull yet. With TinyBSD and mfsBSD I am able to create bootable images, for WRAP 1C and 2E. If I find a solution for NanoBSD, I 'll post it, thanks, Marten -- http://www.voedselbankleiden.nl needs your help! http://martenvijn.nl http://bsd.wifisoft.org/nek/ http://opencommunitycamp.org OCC 2010 ___ 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: 8.0-rc2 meshmode breaks hostap mode on ath0
On Thu, 2009-11-12 at 15:26 +0100, Marten Vijn wrote: hi 8.0-rc2 802.11s breaks ap mode: - on the same interface - when mesh is on diffent channel how-to reproduce: ifconfig wlan0 create wlandev ath0 wlanmode hostap ifconfig wlan0 ssid bert channel 3 up ifconfig wlan1 create wlandev ath0 wlanmode mesh ifconfig wlan1 channel 3 meshid ernie up ifconfig == wlan0 = status: running ifconfig wlan1 channel 7 ifconfig == wlan0 = status: no carrier and is persistent in: 8.0-PRERELEASE tinybsd# uname -a FreeBSD tinybsd.freebsd.org 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE #0 r199257: Tue Nov 17 21:26:00 CET 2009 r...@master:/usr/obj/usr/src/sys/TINYBSD i386 tinybsd# details below, kind regards, Marten dmesg: tinybsd# uname -a FreeBSD tinybsd.freebsd.org 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE #0 r199257: Tue Nov 17 21:26:00 CET 2009 r...@master:/usr/obj/usr/src/sys/TINYBSD i386 tinybsd# dmesg Copyright (c) 1992-2009 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.0-PRERELEASE #0 r199257: Tue Nov 17 21:26:00 CET 2009 r...@master:/usr/obj/usr/src/sys/TINYBSD i386 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Geode(TM) Integrated Processor by National Semi (233.33-MHz 586-class CPU) Origin = Geode by NSC Id = 0x540 Stepping = 0 Features=0x808131FPU,TSC,MSR,CX8,CMOV,MMX real memory = 134217728 (128 MB) avail memory = 120905728 (115 MB) wlan: mac acl policy registered kbd0 at kbdmux0 ACPI Error: A valid RSDP was not found 20090521 tbxfroot-309 ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. pcib0: Host to PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 ath0: Atheros 5212 mem 0x8000-0x8000 irq 12 at device 13.0 on pci0 ath0: [ITHREAD] ath0: AR5212 mac 5.9 RF5112 phy 4.3 sis0: NatSemi DP8381[56] 10/100BaseTX port 0x1000-0x10ff mem 0x8004-0x80040fff irq 10 at device 14.0 on pci0 sis0: Silicon Revision: DP83816A miibus0: MII bus on sis0 nsphyter0: DP83815 10/100 media interface PHY 0 on miibus0 nsphyter0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:0d:b9:05:41:b4 sis0: [ITHREAD] isab0: PCI-ISA bridge port 0xf400-0xf43f,0xf600-0xf63f at device 18.0 on pci0 isa0: ISA bus on isab0 pci0: bridge at device 18.1 (no driver attached) atapci0: National Geode SC1100 ATA33 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 18.2 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: multimedia, audio at device 18.3 (no driver attached) pci0: bridge at device 18.5 (no driver attached) ohci0: OHCI (generic) USB controller mem 0xf000-0xffff irq 9 at device 19.0 on pci0 ohci0: [ITHREAD] usbus0: OHCI (generic) USB controller on ohci0 cpu0 on motherboard pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xe-0xe7fff pnpid ORM on isa0 atrtc0: AT Real Time Clock at port 0x70 irq 8 on isa0 uart0: 16550 or compatible at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 uart0: [FILTER] uart0: console (9600,n,8,1) RTC BIOS diagnostic error 80clock_battery Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 ad0ugen0.1: (0x0e11) at usbus0 uhub0: (0x0e11) OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0 : FAILURE - SETFEATURES SET TRANSFER MODE status=51READY,DSC,ERROR error=4ABORTED ad0: 61MB SanDisk SDCFB-64 Vdg 8.18 at ata0-master BIOSPIO GEOM: ad0: geometry does not match labuhub0: 3 ports with 3 removable, self powered el (4h,32s != 8h,32s). GEOM: ad0: media size does not match label. Trying to mount root from ufs:/dev/ad0a wlan0: Ethernet address: 00:0b:6b:34:58:99 wlan1: Ethernet address: 00:0b:6b:34:58:99 sis0: link state changed to DOWN tinybsd# dmesg: # dmesg Copyright (c) 1992-2009 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.0-RC2 #0: Tue Nov 10 20:24:18 CET 2009 r...@master:/usr/obj/nanobsd.full/usr/src/sys/KERNEL i386 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Enhanced Am486DX4/Am5x86 Write-Back (486-class CPU) Origin = AuthenticAMD Id = 0x494 Stepping = 4 Features=0x1FPU real memory = 67108864 (64 MB) avail memory = 55230464 (52 MB) wlan: mac acl policy registered kbd1 at kbdmux0 ACPI Error: A valid RSDP was not found 20090521 tbxfroot-309 ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. *** WARNING: missing CPU_ELAN -- timekeeping may be wrong pcib0: AMD Elan SC520 host to PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 ath0: Atheros 5212 mem 0xa000-0xa000 irq 10 at device
[releng_8 tinderbox] failure on amd64/amd64
TB --- 2009-11-17 21:15:27 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-17 21:15:27 - starting RELENG_8 tinderbox run for amd64/amd64 TB --- 2009-11-17 21:15:27 - cleaning the object tree TB --- 2009-11-17 21:15:48 - cvsupping the source tree TB --- 2009-11-17 21:15:48 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/amd64/amd64/supfile TB --- 2009-11-17 21:16:17 - building world TB --- 2009-11-17 21:16:17 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-17 21:16:17 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-17 21:16:17 - TARGET=amd64 TB --- 2009-11-17 21:16:17 - TARGET_ARCH=amd64 TB --- 2009-11-17 21:16:17 - TZ=UTC TB --- 2009-11-17 21:16:17 - __MAKE_CONF=/dev/null TB --- 2009-11-17 21:16:17 - cd /src TB --- 2009-11-17 21:16:17 - /usr/bin/make -B buildworld World build started on Tue Nov 17 21:16:18 UTC 2009 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything stage 5.1: building 32 bit shim libraries World build completed on Tue Nov 17 22:43:03 UTC 2009 TB --- 2009-11-17 22:43:03 - generating LINT kernel config TB --- 2009-11-17 22:43:03 - cd /src/sys/amd64/conf TB --- 2009-11-17 22:43:03 - /usr/bin/make -B LINT TB --- 2009-11-17 22:43:03 - building LINT kernel TB --- 2009-11-17 22:43:03 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-17 22:43:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-17 22:43:03 - TARGET=amd64 TB --- 2009-11-17 22:43:03 - TARGET_ARCH=amd64 TB --- 2009-11-17 22:43:03 - TZ=UTC TB --- 2009-11-17 22:43:03 - __MAKE_CONF=/dev/null TB --- 2009-11-17 22:43:03 - cd /src TB --- 2009-11-17 22:43:03 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Nov 17 22:43:03 UTC 2009 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] /src/sys/cam/ata/ata_xpt.c: In function 'ata_scan_lun': /src/sys/cam/ata/ata_xpt.c:1042: error: 'CAM_PRIORITY_NORMAL' undeclared (first use in this function) /src/sys/cam/ata/ata_xpt.c: In function 'ata_device_transport': /src/sys/cam/ata/ata_xpt.c:1179: error: 'CAM_PRIORITY_NORMAL' undeclared (first use in this function) /src/sys/cam/ata/ata_xpt.c: In function 'scsi_set_transfer_settings': /src/sys/cam/ata/ata_xpt.c:1327: error: 'CAM_PRIORITY_NORMAL' undeclared (first use in this function) /src/sys/cam/ata/ata_xpt.c: In function 'scsi_toggle_tags': /src/sys/cam/ata/ata_xpt.c:1441: error: 'CAM_PRIORITY_NORMAL' undeclared (first use in this function) *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-17 22:46:14 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-17 22:46:14 - ERROR: failed to build lint kernel TB --- 2009-11-17 22:46:14 - 3928.28 user 881.40 system 5447.07 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-amd64-amd64.full ___ 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
[releng_8 tinderbox] failure on i386/i386
TB --- 2009-11-17 22:13:36 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-11-17 22:13:36 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2009-11-17 22:13:36 - cleaning the object tree TB --- 2009-11-17 22:14:01 - cvsupping the source tree TB --- 2009-11-17 22:14:01 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/i386/i386/supfile TB --- 2009-11-17 22:14:24 - building world TB --- 2009-11-17 22:14:24 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-17 22:14:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-17 22:14:24 - TARGET=i386 TB --- 2009-11-17 22:14:24 - TARGET_ARCH=i386 TB --- 2009-11-17 22:14:24 - TZ=UTC TB --- 2009-11-17 22:14:24 - __MAKE_CONF=/dev/null TB --- 2009-11-17 22:14:24 - cd /src TB --- 2009-11-17 22:14:24 - /usr/bin/make -B buildworld World build started on Tue Nov 17 22:14:24 UTC 2009 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Tue Nov 17 23:13:12 UTC 2009 TB --- 2009-11-17 23:13:12 - generating LINT kernel config TB --- 2009-11-17 23:13:12 - cd /src/sys/i386/conf TB --- 2009-11-17 23:13:12 - /usr/bin/make -B LINT TB --- 2009-11-17 23:13:12 - building LINT kernel TB --- 2009-11-17 23:13:12 - MAKEOBJDIRPREFIX=/obj TB --- 2009-11-17 23:13:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-11-17 23:13:12 - TARGET=i386 TB --- 2009-11-17 23:13:12 - TARGET_ARCH=i386 TB --- 2009-11-17 23:13:12 - TZ=UTC TB --- 2009-11-17 23:13:12 - __MAKE_CONF=/dev/null TB --- 2009-11-17 23:13:12 - cd /src TB --- 2009-11-17 23:13:12 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Nov 17 23:13:12 UTC 2009 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] /src/sys/cam/ata/ata_xpt.c: In function 'ata_scan_lun': /src/sys/cam/ata/ata_xpt.c:1042: error: 'CAM_PRIORITY_NORMAL' undeclared (first use in this function) /src/sys/cam/ata/ata_xpt.c: In function 'ata_device_transport': /src/sys/cam/ata/ata_xpt.c:1179: error: 'CAM_PRIORITY_NORMAL' undeclared (first use in this function) /src/sys/cam/ata/ata_xpt.c: In function 'scsi_set_transfer_settings': /src/sys/cam/ata/ata_xpt.c:1327: error: 'CAM_PRIORITY_NORMAL' undeclared (first use in this function) /src/sys/cam/ata/ata_xpt.c: In function 'scsi_toggle_tags': /src/sys/cam/ata/ata_xpt.c:1441: error: 'CAM_PRIORITY_NORMAL' undeclared (first use in this function) *** Error code 1 Stop in /obj/i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-11-17 23:16:46 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-11-17 23:16:46 - ERROR: failed to build lint kernel TB --- 2009-11-17 23:16:46 - 2767.16 user 624.06 system 3789.39 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-i386.full ___ 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
HEADS UP: major CAM ATA MFC
Hi. I want to notice, that I've just merged from HEAD to 8-STABLE latest results of my last months work on CAM-based ATA implementation and CAM subsystem itself. Please contact me if you will have any problems, questions, propositions, ... What's done: - major code cleanup. Many SCSIsms in ATA code removed, or reworked for ATA specifics. Many ATA support parts reworked or newly implemented; - CAM code took some fixes and optimizations. Luckily no major changes were required yet. - NCQ support re-factored. Same as for SCSI, non-capable devices now limited by queue depth of 2, to let request sorter do it's job better. - Port Multipliers support re-factored. Is is more stable now. Devices hot-insert/remove supported. Implemented reinitialization after bus resets. - ahci(4) and siis(4) drivers took many changes, including improved timeout handling, error recovery and performance optimizations. - added basic support for PATA transport. After ata(4) drivers wrapper will be finished, it will allow to completely disable old ATA infrastructure. - camcontrol tool now reports more information about ATA devices and supports ATA Power Management. - added support for ATA devices with large sector size, declared by ATA-7 spec (only theoretically now, I haven't seen such yet) - added quirks mechanism for ATA, to allow, for example, to disable NCQ, or later DMA, for specific device model or firmware revision, - added support for DMA-incapable, and some old ATA devices; - implemented ATA error reporting. Things to be done yet: - timeouts and hard errors recovery process with Port Multipliers used can cause deadlocks if happen under heavy load. Any way it is a step forward, as previously it just was not recovering at all. - devices connected using Port Multipliers detected asynchronously, and in some cases they may not get in time for root mounting. - interface mode control possible only using loader tunables, but not with camcontrol. - NCQ is not used for devices with less tags supported then controller capable (it is quite rare). Many thanks to iXsystems Inc for supporting my work, making this all possible. Also thanks to Vitsch Electronics, Sentex Corp, lissyara.su, and many other people for hardware donations. Feedbacks are welcome as always. -- Alexander Motin ___ 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
Support for SAS/SATA non-RAID adapters
I've spent the better part of today doing various web searches in Google, searches in newegg.ca/ncix.com, digging through mailing list archives (-hardware and -stable), man pages, and vendor websites looking for well-supported SATA/SAS adapters for use in FreeBSD storage servers. These servers will be using ZFS, so will not need fancy RAID controllers (currently, we're using 3Ware 9550SXU and 9650SE RAID controllers, which are increasingly hard to buy and very expensive at $1200+ CDN). The chassis have hot-plug SATA backplanes, so can use multi-lane cabling or standard SATA cabling. So far, I've come across a nice selection of LSI and Promise controllers, that are in the $200 - $400 CDN range, and seem to fit the bill. However, I can't find anything that definitively states whether they are supported by FreeBSD 7.x or 8.x. Thus, my questions to all of you: Are any of the following supported by FreeBSD 7/8? If so, by what driver? And do you have any experience (good/bad/otherwise) with any of them? LSI SAS 9211-8i 8-port SAS/SATA PCIe LSI SAS 3081E-R8-port SAS/SATA PCIe LSI SAS 3080X-R8-port SATA/SATA PCI-X Promise SuperTrak EX12350 12-port SATA PCIe Promise SuperTrak EX16350 16-port SATA PCIe Promise SuperTrak EX16300 16-port SATA PCI-X Promise SuperTrak EX16650 16-port SAS/SATA PCIe Any recommendations on other SAS/SATA controllers to look at (just not anything with MegaRAID in the name)? -- Freddie Cash fjwc...@gmail.com ___ 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
vnode_pager_putpages error
FreeBSD 7.2 amd64. Running Apache httpd application (MPM worker threads) and other applications. ZFS file system. After some weeks of uptime, we are seeing these errors repeated many times: vnode_pager_putpages: I/O error 69 vnode_pager_putpages: residual I/O 16384 at 0 After that, httpd dies. On another occasion the entire system rebooted and we are guessing the symptoms are the same, but the console was lost so we can't tell for sure. * Can sometime tell me where I found out what error 69 means? Is there something in the docs somewhere I can look at? * My uninformed guess is that this is some sort of swap/memory exhaustion. Could it be a memory leak in httpd (or one of its modules)? Or could ZFS memory exhaustion be the issue here? If so, we'd probably move to 8.0 as soon as possible with all its ZFS improvements. Any clues to tracking this down would be appreciated. It is a production server and doesn't happen often enough to easily reproduce. Thanks Ari Maniatis -- -- ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A ___ 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: Support for SAS/SATA non-RAID adapters
LSI SAS 3080X-R 8-port SATA/SATA PCI-X This one uses LSI1068 chip which is supported by mpt driver. I'm using motherboard with an on-board equivalent of this and don't have much to complain about. I did see some CRC errors with SATA drives in 3Gbps mode, but those went away after updating firmware to 1.29.0.0. I've seen some comments on zfs-discuss mailing list that -IR variant of the firmware (the one that provides RAID0/1 capabilities) does have some stability issues and recommended going with simpler -IT version (just pass-through disks). --Artem ___ 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: Support for SAS/SATA non-RAID adapters
In general, I've found following page very informative about what's available: http://www.hardforums.com/showthread.php?t=1413050 I've also tried AOC-SAT2-MV8: http://www.supermicro.com/products/accessories/addon/AOC-SAT2-MV8.cfm It's based on Marvell 88sx8061 chipset. Technically it is supported by FreeBSD, but I'd rather stay away from it at least for now. The main issue is that the largest transfer size is 32K. ZFS does push this card hard and under load this card showed noticeably slower transfer rate than LSI1068 under the same circumstances. Folks on zfs-discuss list also mentioned issues with hot-swap on this card on controller level. The somewhat better news is that NetBSD does seem to have much better driver for this marvell chip. If someone gets to port it to FreeBSD, the card may be pretty decent choice for those who have PCI-X slot on-board. --Artem On Tue, Nov 17, 2009 at 6:12 PM, Artem Belevich fbsdl...@src.cx wrote: LSI SAS 3080X-R 8-port SATA/SATA PCI-X This one uses LSI1068 chip which is supported by mpt driver. I'm using motherboard with an on-board equivalent of this and don't have much to complain about. I did see some CRC errors with SATA drives in 3Gbps mode, but those went away after updating firmware to 1.29.0.0. I've seen some comments on zfs-discuss mailing list that -IR variant of the firmware (the one that provides RAID0/1 capabilities) does have some stability issues and recommended going with simpler -IT version (just pass-through disks). --Artem ___ 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: Support for SAS/SATA non-RAID adapters
On Tue, Nov 17, 2009 at 6:12 PM, Artem Belevich fbsdl...@src.cx wrote: LSI SAS 3080X-R 8-port SATA/SATA PCI-X This one uses LSI1068 chip which is supported by mpt driver. I'm using motherboard with an on-board equivalent of this and don't have much to complain about. I did see some CRC errors with SATA drives in 3Gbps mode, but those went away after updating firmware to 1.29.0.0. I've seen some comments on zfs-discuss mailing list that -IR variant of the firmware (the one that provides RAID0/1 capabilities) does have some stability issues and recommended going with simpler -IT version (just pass-through disks). If that one uses the LSI1068 chipset, do you know which one uses the LSI1078 chipset? I've seen that number in the comments in one of the mf* drivers (think it was mfi). How does one determine which actual chipset is in which controller? Do they have that buried in the docs somewhere? I've also found a couple of Areca cards (PCI-X, non-RAID/PCIe RAID), and have heard good things about Areca support in FreeBSD. Any comments on their quality/performance/reliability? -- Freddie Cash fjwc...@gmail.com ___ 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: Support for SAS/SATA non-RAID adapters
Hi, If that one uses the LSI1068 chipset, do you know which one uses the LSI1078 chipset? Supermicro's AOC-USAS-H8iR uses LSI1078: http://www.supermicro.com/products/accessories/addon/AOC-USAS-H8iR.cfm Dell PERC 6/i is based on LSI1078 as well. http://www.dell.com/content/topics/topic.aspx/global/products/pvaul/topics/en/us/raid_controller?c=usl=encs=555 However, these cards are full-blown RAID controllers with their own CPU, memory and corresponding price. I've seen that number in the comments in one of the mf* drivers (think it was mfi). Yes, it is indeed mfi that supports LSI1078. How does one determine which actual chipset is in which controller? Do they have that buried in the docs somewhere? The docs, if you're lucky. Cards listed above mention controller chip explicitly on the product pages. --Artem ___ 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: HEADS UP: major CAM ATA MFC
Alexander Motin wrote: Feedbacks are welcome as always. Today's RELENG_8 build is broken (my /usr/src is symlink to /usr/local/src): # make -j3 MODULES_WITH_WORLD=yes buildworld [skip] === sys/modules/ahci (all) cc -O2 -pipe -march=prescott -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-gr owth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wred undant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointe r-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c / usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c: In function 'ahci_timeout ': /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1286: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c: In function 'ahci_end_tra nsaction': /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1368: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1384: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1396: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1405: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1447: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c: In function 'ahci_reset': /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1703: error: 'struct ahci_ channel' has no member named 'fatalerr' *** Error code 1 Stop in /usr/local/src/sys/modules/ahci. *** Error code 1 Stop in /usr/local/src/sys/modules. *** Error code 1 Stop in /usr/local/src/sys. *** Error code 1 Stop in /usr/local/src. *** Error code 1 Stop in /usr/local/src. *** Error code 1 Stop in /usr/local/src. ___ 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: HEADS UP: major CAM ATA MFC
I didn't have this problem. System has AHCI in use, and the kernel is built to make use of modular atacore. Specifically: # Modular ATA device atacore # Core ATA functionality device ataisa # ISA bus support device atapci # PCI bus support; only generic chipset support device ataahci # AHCI SATA device ataintel# Intel Confirmation: FreeBSD icarus.home.lan 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE #0: Tue Nov 17 20:07:21 PST 2009 r...@icarus.home.lan:/usr/obj/usr/src/sys/X7SBA_RELENG_8_amd64 amd64 world/kernel built with make -j2 buildworld / make -j2 buildkernel. csup last run against cvsup10.freebsd.org approximately 2 hours ago. I did notice a number of commits to ATA, XPT, CAM, etc. ~8-10 hours ago as well, but even more ~2 hours ago. I assume the delays are due to what the cvsup master vs. mirrors have and how often they sync. I'd recommend you re-csup with a different mirror and see if there are any changes. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | On Wed, Nov 18, 2009 at 01:04:37PM +0700, Eugene Grosbein wrote: Alexander Motin wrote: Feedbacks are welcome as always. Today's RELENG_8 build is broken (my /usr/src is symlink to /usr/local/src): # make -j3 MODULES_WITH_WORLD=yes buildworld [skip] === sys/modules/ahci (all) cc -O2 -pipe -march=prescott -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-gr owth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wred undant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointe r-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c / usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c: In function 'ahci_timeout ': /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1286: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c: In function 'ahci_end_tra nsaction': /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1368: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1384: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1396: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1405: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1447: error: 'struct ahci_ channel' has no member named 'fatalerr' /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c: In function 'ahci_reset': /usr/local/src/sys/modules/ahci/../../dev/ahci/ahci.c:1703: error: 'struct ahci_ channel' has no member named 'fatalerr' *** Error code 1 Stop in /usr/local/src/sys/modules/ahci. *** Error code 1 Stop in /usr/local/src/sys/modules. *** Error code 1 Stop in /usr/local/src/sys. *** Error code 1 Stop in /usr/local/src. *** Error code 1 Stop in /usr/local/src. *** Error code 1 Stop in /usr/local/src. ___ 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 ___ 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: HEADS UP: major CAM ATA MFC
Jeremy Chadwick wrote:
I didn't have this problem. System has AHCI in use, and the kernel is
built to make use of modular atacore. Specifically:
[skip]
I'd recommend you re-csup with a different mirror and see if there are
any changes.
I'll try. By the way, have you used MODULES_WITH_WORLD while building world?
RELENG_8 still has a couple of other problems with this knob, needed patches
are:
-- sys/modules/dtrace/lockstat/Makefile.orig2009-09-16 23:05:25.0
+0800
+++ sys/modules/dtrace/lockstat/Makefile2009-09-16 23:05:45.0
+0800
@@ -5,7 +5,7 @@
KMOD= lockstat
SRCS= lockstat.c
-SRCS+= vnode_if.h
+SRCS+= vnode_if.h opt_kdtrace.h
CFLAGS+= -I${.CURDIR}/../../../cddl/compat/opensolaris \
-I${.CURDIR}/../../../cddl/contrib/opensolaris/uts/common \
--- sys/modules/sysvipc/sysvmsg/Makefile.orig 2009-09-16 23:04:00.0
+0800
+++ sys/modules/sysvipc/sysvmsg/Makefile2009-09-16 23:04:12.0
+0800
@@ -3,6 +3,6 @@
.PATH: ${.CURDIR}/../../../kern
KMOD= sysvmsg
-SRCS= sysv_msg.c opt_sysvipc.h
+SRCS= sysv_msg.c opt_sysvipc.h opt_compat.h
.include bsd.kmod.mk
--- sys/modules/sysvipc/sysvsem/Makefile.orig 2009-09-16 23:02:02.0
+0800
+++ sys/modules/sysvipc/sysvsem/Makefile2009-09-16 23:01:51.0
+0800
@@ -3,6 +3,6 @@
.PATH: ${.CURDIR}/../../../kern
KMOD= sysvsem
-SRCS= sysv_sem.c opt_sysvipc.h
+SRCS= sysv_sem.c opt_sysvipc.h opt_compat.h
.include bsd.kmod.mk
___
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
boot issues
[ this happened a month ago and i backed off ] i386, 7.2-stable from last summer cvsupped releng_7 made and installed kernel buildworld boot -s installworld mergemaster reboot hung after beastie, just as it did the other month booted -s mount -2 / /etc/rc.d/hostid start /etc/rc.d/zfs start looked around and all seemed ok ^D came up ok and that is how it is running now but why will it boot through -s and not from beastie? randy ___ 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: Support for SAS/SATA non-RAID adapters
On Tue, Nov 17, 2009 at 08:38:21PM -0800, Freddie Cash wrote: I've also found a couple of Areca cards (PCI-X, non-RAID/PCIe RAID), and have heard good things about Areca support in FreeBSD. Any comments on their quality/performance/reliability? I have got an Areca ARC-1110 4x SATA2 PCI-X card in my server, and I'm quite impressed with the performance; these cards do very well in terms I/O operations per second and the driver has been rock solid for me. The only downside is that they are quite expensive (but well worth it, IMO) Regards, -- Rink P.W. Springer- http://rink.nu Beauty often seduces us on the road to truth. - Dr. Wilson ___ 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: HEADS UP: major CAM ATA MFC
Eugene Grosbein wrote: Alexander Motin wrote: Feedbacks are welcome as always. Today's RELENG_8 build is broken (my /usr/src is symlink to /usr/local/src): Can you try to update your sources again? ahci driver in 8-STABLE and HEAD are identical now and building fine in both, I've checked it yesterday. -- Alexander Motin ___ 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: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
Did newfs on those partition and made things worsen -- restore completely fails: (I had experienced another similar problem on an IDE, which works well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. Is something new in 8.0 making disk partition schema changed? g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 fopen: Device not configured cannot create save file ./restoresymtable for symbol table abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scs i status == 0x0 (da0:umass-sim0:0:0:0): removing device entry ugen1.2: DMI at usbus1 umass0: DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: DMI Ultra HDD 1.19 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) Device da0s3d went missing before all of the data could be written to it; expect data loss. 99 23:19 sysinstall 100 23:20 newfs /dev/da0s3d 101 23:20 newfs /dev/da0s3e 102 23:21 mount /dev/da0s3d /mnt 103 23:21 cd /mnt 104 23:21 dump -0f - /home | restore -rf - 105 23:27 history 15 -Original Message- From: Guojun Jin Sent: Tue 11/17/2009 11:05 PM To: freebsd-stable@freebsd.org Cc: questi...@freebsd.org; freebsd-...@freebsd.org Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ 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
