From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 30 17:09:00 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63EEC16A4CE for ; Mon, 30 Aug 2004 17:09:00 +0000 (GMT) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1CC043D31 for ; Mon, 30 Aug 2004 17:08:58 +0000 (GMT) (envelope-from valery@no-log.org) Received: from [192.168.0.22] (gambetta-2-82-67-185-6.fbx.proxad.net [82.67.185.6]) by postfix3-1.free.fr (Postfix) with ESMTP id 8114A173BEB for ; Mon, 30 Aug 2004 19:08:57 +0200 (CEST) Message-ID: <41335F0C.5030400@no-log.org> Date: Mon, 30 Aug 2004 19:08:28 +0200 From: =?ISO-8859-1?Q?Val=E9ry?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [5.2.1] - Kernel/Memory segmentation fault : a solution. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2004 17:09:00 -0000 Hello, i met an error when compiling a new kernel : "Memory error : segmentation fault" (i tried to compile orginal GENERIC and my own, and the same result appear). This kinds of computing stress the memory, and if you have a bad one, you'll get this message. Changing my 256Mo memory to a "10 years guaranted", exactly what is specified by the mobo, the trouble continued. Because i'm using an IGP graphic card, you must know that this one use the main memory to allocate his own. For example, when you boot, if you have installed 256Mo of main memory, system say that you have only 192Mo, and it's right, the IGP allocate 64Mo for his own space. So, knowing that, perhaps signals between BSD and the mobo are not clear, and this will explain my "memory fault" (system trying to use more than available for him ?.., i don't know, because BSD say well that i have 192Mo, not 256). Thus, searching, i have found a solution to avoid that : you "must" just add one parameter in loader.conf, and all will be nice : /boot/loader.conf hw.physmem="your_exact_ammount_of_memoryM" you can specify hw.physmem="128M", or "131072K", or use the suffix G for 1Go, and so one (see loader(8)) Setting this parameter was good for me, my new kernel compile without error, even with my old memory. This tips perhaps will avoid to someone to buy a very expensive "10 years guaranted" memory. Regards to the community, -- v/ From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 30 18:18:15 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0899216A4D0 for ; Mon, 30 Aug 2004 18:18:15 +0000 (GMT) Received: from fmmailgate03.web.de (fmmailgate03.web.de [217.72.192.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA0DB43D60 for ; Mon, 30 Aug 2004 18:18:13 +0000 (GMT) (envelope-from lukas@razik.de) Received: by fmmailgate03.web.de (8.12.6/8.12.6/webde Linux 0.7) with SMTP id i7UIHJUS031376 for freebsd-hardware@freebsd.org; Mon, 30 Aug 2004 20:18:12 +0200 Received: from 217.95.123.152 by freemailng5303.web.de with HTTP; Mon, 30 Aug 2004 20:18:11 +0200 Date: Mon, 30 Aug 2004 20:18:11 +0200 Message-Id: <163331489@web.de> MIME-Version: 1.0 From: "Lukas Razik" To: freebsd-hardware@freebsd.org Precedence: fm-user X-WEBDE-Sender: Organization: http://freemail.web.de/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: [5.3-BETA2] acd0: FAILURE - READ_BIG HARDWARE ERROR X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2004 18:18:15 -0000 Hi!!! I've a little problem with the 5.3-BETA2 because If I try to mount the acd0 device it doesn't work. I always get this: acd0: FAILURE - READ_BIG HARDWARE ERROR asc=0x08 ascq=0x03 error=0 No problems with acd1. Another error message I get is: Interrupt storm detected on "irq11: acpi0"; throttling interrupt source I had no other errors/panics during installation and the rest of the system works fine. There were no problems with earlier 5.X.X and my acd0: DVDROM at ata0-master UDMA66 Regards, Lukas Here the whole dmesg: =================== 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-BETA2 #1: Sat Aug 28 21:29:15 UTC 2004 root@mack.dcsl.buffalo.edu:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (801.82-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383fbff real memory = 1610547200 (1535 MB) avail memory = 1568518144 (1495 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 pcib0: port 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pcib0: could not get PCI interrupt routing table for \\_SB_.PCI0 - AE_BAD_DATA pci0: on pcib0 pcib0: no PRT entry for 0.7.INTD agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib0: no PRT entry for 0.1.INTA pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xc000-0xc00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0xc400-0xc41f irq 9 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) fxp0: port 0xc800-0xc81f mem 0xe7000000-0xe70fffff,0xe7103000-0xe7103fff irq 17 at device 9.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:a0:c9:c5:8a:24 fxp0: [GIANT-LOCKED] uhci1: port 0xcc00-0xcc1f irq 18 at device 10.0 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ugen0: SiW SiW, rev 1.10/15.00, addr 2 uhci2: port 0xd000-0xd01f irq 19 at device 10.1 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uscanner0: EPSON EPSON Scanner, rev 2.00/1.00, addr 2 pci0: at device 10.2 (no driver attached) atapci1: port 0xe400-0xe4ff,0xe000-0xe003,0xdc00-0xdc07,0xd800-0xd803,0xd400-0xd407 irq 16 at device 11.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pcib2: at device 12.0 on pci0 pci2: on pcib2 mlx0: mem 0xe7100000-0xe7101fff irq 18 at device 12.1 on pci0 mlx0: [GIANT-LOCKED] mlx0: DAC960PG, 3 channels, firmware 4.06-0-08, 8MB RAM mlxd0: on mlx0 mlxd0: 26280MB (53821440 sectors) RAID 5 (online) mlxd1: on mlx0 mlxd1: 8678MB (17772544 sectors) RAID 1 (online) pcm0: port 0xe800-0xe83f irq 19 at device 13.0 on pci0 pcm0: pcm0: [GIANT-LOCKED] fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 orm0: at iomem 0xd4000-0xd6fff,0xd0000-0xd3fff,0xc0000-0xcffff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 10.000 msec ATAPI_RESET time = 40us acd0: DVDROM at ata0-master UDMA66 ATAPI_RESET time = 140us acd1: CDRW at ata1-slave PIO4 ad4: 28629MB [58168/16/63] at ata2-master UDMA100 ad6: 28629MB [58168/16/63] at ata3-master UDMA100 ar0: 57259MB [7299/255/63] status: READY subdisks: disk0 READY on ad4 at ata2-master disk1 READY on ad6 at ata3-master SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/mlxd0s1a Interrupt storm detected on "irq11: acpi0"; throttling interrupt source acd0: FAILURE - READ_BIG HARDWARE ERROR asc=0x08 ascq=0x03 error=0 From owner-freebsd-hardware@FreeBSD.ORG Tue Aug 31 07:43:06 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8248216A4CE for ; Tue, 31 Aug 2004 07:43:06 +0000 (GMT) Received: from viger.playstos.com (viger.playstos.com [81.208.22.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED93843D48 for ; Tue, 31 Aug 2004 07:43:05 +0000 (GMT) (envelope-from demanzano@playstos.com) Received: from sunshine.playstos.ldr (gw2.playstos.com [81.208.22.130]) by viger.playstos.com (Postfix) with ESMTP id DE3CB20682 for ; Tue, 31 Aug 2004 09:43:03 +0200 (CEST) Date: Tue, 31 Aug 2004 09:43:03 +0200 From: Alessandro de Manzano Organization: Playstos - TIMA SpA X-Priority: 3 (Normal) Message-ID: <63693778203.20040831094303@playstos.com> To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: USB (2.0?) / firewire support for external HD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Alessandro de Manzano List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2004 07:43:06 -0000 Hello, I'm deploying a new server (probably some kind of Dell PowerEdge) with FreeBSD 4.10-Release and I'ld know your experiences with USB and/or firewire (IEEE 1394) connected external hard drives (like LaCie's or similar) Are they working correctly ? how about IEEE1394 and USB2 support in 4.10-release ? (my experience is limited to USB1 for stuff like keyboards and mice) Any hint and suggestions more than welcome ! Many thanks in advance! -- Alessandro de Manzano System & Network Administrator Playstos - TIMA S.p.A. Corso Sempione 63 20149 Milano, Italy tel.: +39-023314153 fax : +39-02315678 email: demanzano@playstos.com http://www.playstos.com From owner-freebsd-hardware@FreeBSD.ORG Tue Aug 31 10:04:15 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6BD616A4EE for ; Tue, 31 Aug 2004 10:04:14 +0000 (GMT) Received: from croclist.gatorhole.com (213-150-135-231.telenor.se [213.150.135.231]) by mx1.FreeBSD.org (Postfix) with SMTP id 54DAC43D58 for ; Tue, 31 Aug 2004 10:04:13 +0000 (GMT) (envelope-from prl@gatorhole.se) Received: (qmail 11838 invoked by uid 1000); 31 Aug 2004 10:01:35 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Aug 2004 10:01:35 -0000 Date: Tue, 31 Aug 2004 12:01:35 +0200 (MEST) From: Ragnar Lonn X-X-Sender: To: In-Reply-To: Message-ID: X-ALLYOURBASEAREBELONGTO: Us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: sio/puc config problems X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2004 10:04:15 -0000 Hi again, My troubles with Lavalink's card and sio/puc continues. I added a second serial port to the Lavalink Dserial card configuration entry in pucdata.c and then used in the kernel config: device puc0 at pci? port 0x4000 flags 0x205 device puc1 at pci? port 0x4008 irq 15 flags 0x205 # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 But while the boot messages look more promising I still don't get any working serial ports (except for COM1/sio0): found-> vendor=0x1407, dev=0x0110, revid=0x00 class=07-00-02, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base 00004000, size 3 found-> vendor=0x1407, dev=0x0111, revid=0x00 class=07-00-02, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 3, range 32, base 00004008, size 3 pci7: on pcib7 puc0: port 0x4000-0x4007 irq 15 at device 5.0 on pci7 using shared irq15. could not get resource sio1: irq maps: 0x3 0x8007 0x3 0x3 sio1: probe failed test(s): 9 puc1: port 0x4008-0x400f irq 15 at device 5.1 on pci7 could not get resource sio2: irq maps: 0x3 0x8007 0x8007 0x3 sio2: probe failed test(s): 4 6 Apparently, the sio1 and sio2 ports fail on some tests (but not the same on both ports?) And is "could not get resource" a show-stopper or not? If anyone could explain to me a little more in-depth the various parameters used by sio and puc I'd be willing to write some documentation about it all. I have seen several people ask for help with their serial port problems and the only decent documentation is the sio man file, which doesn't help much when something doesn't work. Anyway, any help at all is appreciated of course. Regards, /Ragnar On Tue, 24 Aug 2004, Ragnar Lonn wrote: > Hi all, > > I'm trying to get a Lavalink DSerial 3.3V PCI-X card to > work on FreeBSD 4.10 but with no luck so far. > > The machine is a HP Proliant DL360. We compiled in the puc driver and now > it sees the card as: > > puc0: port 0xfff8-0xffff irq 15 at device 5.0 on pci7 > > Below is the dmesg output. Does anyone have any clues as to how to get all > three serial ports (the original, COM1 on the motherboard plus the two > ports on the Lava card) to work? > > Regards, > > /Ragnar > > > pcib1: on motherboard > pci1: on pcib1 > ciss0: port 0x3000-0x30ff mem 0xf7ef0000-0xf7ef3fff,0xf7fc0000-0xf7ffffff irq 11 at device 4.0 on pci1 > bge0: mem 0xf7fb0000-0xf7fbffff irq 5 at device 5.0 on pci1 > bge0: Ethernet address: 00:0b:cd:1b:33:bd > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > pcib0: on motherboard > pci0: on pcib0 > pci0: at 3.0 irq 7 > pci0: (vendor=0x0e11, dev=0xb203) at 5.0 irq 3 > pci0: (vendor=0x0e11, dev=0xb204) at 5.2 irq 15 > isab0: at device 15.0 on pci0 > isa0: on isab0 > atapci0: port 0-0x3,0x2000-0x200f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pcib2: on motherboard > pci2: on pcib2 > pcib7: on motherboard > pci7: on pcib7 > puc0: port 0xfff8-0xffff irq 15 at device 5.0 on pci7 > sio1: type 16550A > pci7: (vendor=0x1407, dev=0x0111) at 5.1 irq 0 > pcib3: on motherboard > pci3: on pcib3 > eisa0: on motherboard > mainboard0: on eisa0 slot 0 > orm0: