From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 6 06:24:14 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 3184D16A4CE for ; Tue, 6 Apr 2004 06:24:14 -0700 (PDT) Received: from mail.npd.ufsc.br (webmail.npd.ufsc.br [150.162.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D77643D54 for ; Tue, 6 Apr 2004 06:24:09 -0700 (PDT) (envelope-from carlson@npd.ufsc.br) Received: from localhost (localhost [127.0.0.1]) by mail.npd.ufsc.br (Postfix) with ESMTP id 3E10D91CC for ; Tue, 6 Apr 2004 10:23:02 -0300 (EST) Received: from npd.ufsc.br (balantidium.interop.ufsc.br [150.162.248.5]) by mail.npd.ufsc.br (Postfix) with ESMTP id 9566D91C0 for ; Tue, 6 Apr 2004 10:23:00 -0300 (EST) Message-ID: <4072AF32.9060506@npd.ufsc.br> Date: Tue, 06 Apr 2004 10:22:58 -0300 From: Augusto Castelan Carlson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116 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 X-Virus-Scanned: by AMaViS 0.3.12pre8 Subject: NICs not reconized - FreeBSD 4.9 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, 06 Apr 2004 13:24:14 -0000 Hi, I have an Encore interface card with RealTek 8169s chipset and an integrated Broadcom 5788. For the first one I tried to install the FreeBSD driver from RealTek web site without success. I got from this site: http://people.freebsd.org/~wpaul/RealTek/4-stable/re.tar.gz another driver and compiled the kernel, but on boot it reconizes another chipset (below) and the auto select always get 10Mbps Half. I would like to get 1Gbps. dmesg output: re0: port 0xec00-0xecff mem 0xdffff f00-0xdfffffff irq 10 at device 7.0 on pci0 What are the correct steps to install this realtek driver correctely? And the broadcom 5788, can I make it work on FreeBSD 4.9? Thanks in advance, Augusto From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 6 19:55:22 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 9FED316A4D4 for ; Tue, 6 Apr 2004 19:55:22 -0700 (PDT) Received: from ms-smtp-01-eri0.southeast.rr.com (ms-smtp-01-lbl.southeast.rr.com [24.25.9.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2660D43D39 for ; Tue, 6 Apr 2004 19:55:17 -0700 (PDT) (envelope-from jason@ec.rr.com) Received: from ec.rr.com (cpe-024-211-231-149.ec.rr.com [24.211.231.149]) i372reSm019985; Tue, 6 Apr 2004 22:53:41 -0400 (EDT) Message-ID: <40736DD9.2090007@ec.rr.com> Date: Tue, 06 Apr 2004 22:56:25 -0400 From: jason User-Agent: Mozilla Thunderbird 0.5 (X11/20040330) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Augusto Castelan Carlson References: <4072AF32.9060506@npd.ufsc.br> In-Reply-To: <4072AF32.9060506@npd.ufsc.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine cc: freebsd-hardware@freebsd.org Subject: Re: NICs not reconized - FreeBSD 4.9 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: Wed, 07 Apr 2004 02:55:22 -0000 Augusto Castelan Carlson wrote: > Hi, > > I have an Encore interface card with RealTek 8169s chipset and an > integrated Broadcom 5788. > > For the first one I tried to install the FreeBSD driver from RealTek > web site without success. I got from this site: > http://people.freebsd.org/~wpaul/RealTek/4-stable/re.tar.gz > another driver and compiled the kernel, but on boot it reconizes > another chipset (below) and the auto select always get 10Mbps Half. I > would like to get 1Gbps. > > dmesg output: > re0: port 0xec00-0xecff > mem 0xdffff > f00-0xdfffffff irq 10 at device 7.0 on pci0 > > What are the correct steps to install this realtek driver correctely? > And the broadcom 5788, can I make it work on FreeBSD 4.9? > > Thanks in advance, > > Augusto > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" > Did the default driver in bsd not work? I would not compile it in until I found one that worked. Just load and unload modules, it makes life easy. You could try to tweak the default driver to recgonize your card and it may just work. Since you downloaded the driver you could try looking at the differences between the web and system drivers with diff, it may be 95% the same. From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 6 21:29:27 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 5102716A4CE for ; Tue, 6 Apr 2004 21:29:27 -0700 (PDT) Received: from venus.unixlabplus.com (h-67-100-145-26.nycmny83.covad.net [67.100.145.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8812F43D46 for ; Tue, 6 Apr 2004 21:29:26 -0700 (PDT) (envelope-from mwang@unixlabplus.com) Received: from venus.unixlabplus.com (localhost [127.0.0.1]) by venus.unixlabplus.com (8.12.5/8.12.5) with ESMTP id i374SMP4001109 for ; Wed, 7 Apr 2004 00:28:22 -0400 (EDT) Received: (from mwang@localhost) by venus.unixlabplus.com (8.12.5/8.12.5/Submit) id i374SLqw001108 for freebsd-hardware@FreeBSD.ORG; Wed, 7 Apr 2004 00:28:21 -0400 (EDT) Date: Wed, 7 Apr 2004 00:28:21 -0400 From: Michael Wang To: freebsd-hardware@FreeBSD.ORG Message-ID: <20040407042821.GB1060@unixlabplus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: 4.9-R panic with Lava DSerial-PCI 3.3v and device puc 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: Wed, 07 Apr 2004 04:29:27 -0000 I posted it in freebsd-questions, but no response. I try my luck here. This hardware is supported, but it panics. Thanks. (0) Hardware: - Dell 1750 - 133 MHz 3.3v PCIX - Lava DSerial-PCI 3.3v Software: - FreeBSD 4.9-R - device puc (1) without "device puc", upon boot, I have pcib3: on motherboard pci3: on pcib3 pci3: (vendor=0x1407, dev=0x0110) at 6.0 irq 0 pci3: (vendor=0x1407, dev=0x0111) at 6.1 irq 0 pcib4: on motherboard pci4: on pcib4 pciconf -lv shows: none1@pci3:6:0: class=0x070002 card=0x01101407 chip=0x01101407 rev=0x00 hdr=0x00 vendor = 'Lava Computer Manufacturing Inc' device = 'Lava DSerial PCI Port A' class = simple comms subclass = UART none2@pci3:6:1: class=0x070002 card=0x01111407 chip=0x01111407 rev=0x00 hdr=0x00 vendor = 'Lava Computer Manufacturing Inc' device = 'Lava DSerial PCI Port B' class = simple comms subclass = UART (2) after adding options COM_MULTIPORT device puc device sio I have the following upon boot. Please note "irq 0". pcib3: on motherboard pci3: on pcib3 puc0: irq 0 at device 6.0 on pci3 pci_cfgintr_virgin: using routable interrupt 4 kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0xbc7c fault code = supervisor read, page not present instruction pointer = 0x8:0xc00fcd24 stack pointer = 0x10:0xc057cd94 frame pointer = 0x10:0xc057ce04 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam kernel: type 12 trap, code=0 Stopped at 0xc00fcd24: movb %cs:0xbc7c,%al db> trace kernbase(40a,c057ce44,c032cc03,c318f180,c057ce44) at 0xc00fcd24 db> ps pid proc addr uid ppid pgrp flag stat wmesg wchan cmd 2 dc05ec60 dda66000 0 0 0 000204 2 taskqueue 1 dc05ee00 dc063000 0 0 0 000204 2 swapper 0 c04bbe00 c057a000 0 0 0 000204 2 swapper (3) General questions: >From various documentation: " options "COM_MULTIPORT" device sio4 at isa? port 0x2a0 tty flags 0x781 device sio5 at isa? port 0x2a8 tty flags 0x781 device sio6 at isa? port 0x2b0 tty flags 0x781 device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr " My questions are: (3a) My device is PCI device, should I use isa? Why all documentation on sio uses isa? (3b) How do I know the port number? minor number? irq? And what is "vector siointr"? Looks like "tty", and "vector siointr" are illegal in 4.9-R. (3c) I have Lava DSerial-PCI 3.3v, should I use this? options "COM_MULTIPORT" device puc device sio4 at isa? port 0x2a0 flags 0x581 device sio5 at isa? port 0x2a8 flags 0x581 irq 11 Thanks a lot. -- Michael Wang * http://www.unixlabplus.com/ * mwang@unixlabplus.com From owner-freebsd-hardware@FreeBSD.ORG Wed Apr 7 06:02:02 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 A57D716A4CE for ; Wed, 7 Apr 2004 06:02:02 -0700 (PDT) Received: from mail.npd.ufsc.br (mail.npd.ufsc.br [150.162.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DCC343D3F for ; Wed, 7 Apr 2004 06:02:00 -0700 (PDT) (envelope-from carlson@npd.ufsc.br) Received: from localhost (localhost [127.0.0.1]) by mail.npd.ufsc.br (Postfix) with ESMTP id 04A7E93A0; Wed, 7 Apr 2004 09:59:59 -0300 (EST) Received: from npd.ufsc.br (balantidium.interop.ufsc.br [150.162.248.5]) by mail.npd.ufsc.br (Postfix) with ESMTP id 32C449398; Wed, 7 Apr 2004 09:59:58 -0300 (EST) Message-ID: <4073FB4D.3060901@npd.ufsc.br> Date: Wed, 07 Apr 2004 09:59:57 -0300 From: Augusto Castelan Carlson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jason References: <4072AF32.9060506@npd.ufsc.br> <40736DD9.2090007@ec.rr.com> In-Reply-To: <40736DD9.2090007@ec.rr.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS 0.3.12pre8 cc: freebsd-hardware@freebsd.org Subject: Re: NICs not reconized - FreeBSD 4.9 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: Wed, 07 Apr 2004 13:02:02 -0000 jason wrote: >> What are the correct steps to install this realtek driver correctely? >> And the broadcom 5788, can I make it work on FreeBSD 4.9? >> >> > Did the default driver in bsd not work? I would not compile it in until > I found one that worked. Just load and unload modules, it makes life > easy. You could try to tweak the default driver to recgonize your card > and it may just work. Since you downloaded the driver you could try > looking at the differences between the web and system drivers with diff, > it may be 95% the same. I suppose that there is no default driver for these NICs, as they are not reconized during the system install. I know that they work on FreeBSD 5.2.1, but the application that I'm intend to use only works on version 4.x. About loading and unload modules, I have to do that using /boot/loader.conf or there is a command line to do it? It's not dangerous to tweak the code? Can I damage the NIC? Thanks, Augusto From owner-freebsd-hardware@FreeBSD.ORG Wed Apr 7 07:08:35 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 0DBF516A4CE for ; Wed, 7 Apr 2004 07:08:35 -0700 (PDT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 802E743D49 for ; Wed, 7 Apr 2004 07:08:34 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])i37DJv5v004517; Wed, 7 Apr 2004 23:19:57 +1000 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i37DJsGQ014679; Wed, 7 Apr 2004 23:19:56 +1000 Date: Wed, 7 Apr 2004 23:19:53 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Michael Wang In-Reply-To: <20040407042821.GB1060@unixlabplus.com> Message-ID: <20040407222807.Y11144@gamplex.bde.org> References: <20040407042821.GB1060@unixlabplus.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hardware@FreeBSD.org Subject: Re: 4.9-R panic with Lava DSerial-PCI 3.3v and device puc 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: Wed, 07 Apr 2004 14:08:35 -0000 On Wed, 7 Apr 2004, Michael Wang wrote: > I posted it in freebsd-questions, but no response. I try > my luck here. This hardware is supported, but it panics. > .... > (1) > > without "device puc", upon boot, I have > > pcib3: on motherboard > pci3: on pcib3 > pci3: (vendor=0x1407, dev=0x0110) at 6.0 irq 0 > pci3: (vendor=0x1407, dev=0x0111) at 6.1 irq 0 > pcib4: on motherboard > pci4: on pcib4 irq 0 is from the card's PCI registers. The irq should be nonzero here. This is hard to recover from, and FreeBSD-4.9 apparently doesn't manage to figure out the actual irq. Look at BIOS boot messages to see if the BIOS prints a useable irq number. My guess is that it doesn't. > pciconf -lv shows: > > none1@pci3:6:0: class=0x070002 card=0x01101407 chip=0x01101407 rev=0x00 hdr=0x00 > vendor = 'Lava Computer Manufacturing Inc' > device = 'Lava DSerial PCI Port A' > class = simple comms > subclass = UART > none2@pci3:6:1: class=0x070002 card=0x01111407 chip=0x01111407 rev=0x00 hdr=0x00 > vendor = 'Lava Computer Manufacturing Inc' > device = 'Lava DSerial PCI Port B' > class = simple comms > subclass = UART Also look at boot -v messages. > > (2) > after adding > options COM_MULTIPORT > device puc > device sio > > I have the following upon boot. Please note "irq 0". Leave out COM_MULTIPORT (it is for old isa multiport cards). Otherwise, this is the correct (software) configuration, but it won't work if the irq ends up being 0. > > pcib3: on motherboard > pci3: on pcib3 > puc0: irq 0 at device 6.0 on pci3 > pci_cfgintr_virgin: using routable interrupt 4 > kernel trap 12 with interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xbc7c > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc00fcd24 > stack pointer = 0x10:0xc057cd94 > frame pointer = 0x10:0xc057ce04 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 0 (swapper) > interrupt mask = net tty bio cam > kernel: type 12 trap, code=0 > Stopped at 0xc00fcd24: movb %cs:0xbc7c,%al > db> trace > kernbase(40a,c057ce44,c032cc03,c318f180,c057ce44) at 0xc00fcd24 The instruction pointer is in the ROM BIOS. This seems to be from a vm86 call. "trace" doesn't work for (traps in) vm86 calls because it doesn't understand the stack frame. Apparently pci interrupt initialization made a bad vm86 call because it doesn't understand irq 0. > > General questions: > > >From various documentation: > > " > options "COM_MULTIPORT" > device sio4 at isa? port 0x2a0 tty flags 0x781 > device sio5 at isa? port 0x2a8 tty flags 0x781 > device sio6 at isa? port 0x2b0 tty flags 0x781 > device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr > " sio(4) is unfortunately out of date. It doesn't even mention puc(4). The above is essentially only for isa cards. However, if you know the i/o addresses (and the irq!) then you can handle many pci sio cards by pretending that you have and isa card and specifying the addresses as above (but more correctly). > My questions are: > > (3a) My device is PCI device, should I use isa? No. > Why all documentation on sio uses isa? It's out of date in RELENG_4 :-(. -current is a bit better. It says to just use "device sio" for pci cards. It doesn't say that "device puc" is also needed for most pci cards. The addresses don't need to be specified for pci if you have a supported card. However, if you have an unsupported card, then specifying the addresses is even harder -- you must determine the pci BARs and other pci magic for the card and enter them in pucdata.c. This is not the problem here, since the Lava card is supported. > (3b) How do I know the port number? minor number? irq? For isa cards and pci cards fudged as isa cards, the port address is wherever it is; then minor number is whatever you want (but must be between 0 and 31), and the irq is wherever it is. isa port addresses and irq numbers are normally fixed or statically configured using jumpers, DIP switches or BIOS setup. pci port addresses and irq numbers are mostly dynamically configured (PCI slot numbers often affect the irq, and some BIOS setups/hardware support programming specific irq numbers). Normally they don't change unless the hardware changes. To fudge a pci device as an isa one, first determine these values. You already know the (wrong) irq number. If nothing dynamically allocates the irq then there won't by a correct one. Similarly for the port address. The port addresses would be printed by the probe if it didn't crash. They can be determined by looking at the card's pci registers (pciconf -lv doesn't know quite enough to show them). However, if nothing dynamically allocates them, then they may be 0 like the irq. > And what is "vector siointr"? Looks like "tty", and "vector siointr" > are illegal in 4.9-R. See the 4.x man page for sio. These went away long ago, and the man page is not out of date enough to mention them. > > (3c) I have Lava DSerial-PCI 3.3v, should I use this? > > options "COM_MULTIPORT" > device puc > device sio4 at isa? port 0x2a0 flags 0x581 > device sio5 at isa? port 0x2a8 flags 0x581 irq 11 Not except as a hack; see above. Bruce From owner-freebsd-hardware@FreeBSD.ORG Wed Apr 7 09:30:59 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 132EF16A4CE; Wed, 7 Apr 2004 09:30:59 -0700 (PDT) Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1E8E43D2D; Wed, 7 Apr 2004 09:30:57 -0700 (PDT) (envelope-from matrix@itlegion.ru) Received: from artem (artem.office.ipform.ru [192.168.0.12]) by osiris.ipform.ru (8.12.6/8.12.6) with ESMTP id i37GToXg046620; Wed, 7 Apr 2004 20:29:50 +0400 (MSD) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <000c01c41cbd$0399e330$0c00a8c0@artem> From: "Artem Koutchine" To: Date: Wed, 7 Apr 2004 20:25:54 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: freebsd-bugs@freebsd.org cc: freebsd-hardware@freebsd.org Subject: lock order reversal and swap 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: Wed, 07 Apr 2004 16:30:59 -0000 This evening, before going hove i decided to load-test the new server. I remind the server is: dual xeon 2.66, 2GB ECC ram, supermicro x5dpeg2 mb, 3ware 8506-4LP sata radi controller, 4 sata seagate disks, eveyrthing is install in a RAID5 array. I run: 3 bonnies in a loop, 4 byteneches in a loop, 6 my own perl scripts to test the memory. Each allocated about 256MB ran, fill it with somethingm then free and do it over and over again. After 3 minutes of running i saw this: Apr 7 20:16:34 new kernel: lock order reversal Apr 7 20:16:34 new kernel: 1st 0xc79446b4 vm object (vm object) @ /usr/src/sys/vm/swap_pager.c:1313 Apr 7 20:16:35 new kernel: 2nd 0xc08b9e00 swap_pager swhash (swap_pager swhash) @ /usr/src/sys/vm/swap_pager.c:1803 Apr 7 20:16:35 new kernel: 3rd 0xc7898294 vm object (vm object) @ /usr/src/sys/vm/uma_core.c:886 Apr 7 20:16:35 new kernel: Stack backtrace: Apr 7 20:16:35 new kernel: backtrace(0,1,c0888798,c08898f0,c08174bc) at backtrace+0x12 Apr 7 20:16:35 new kernel: witness_checkorder(c7898294,9,c07d43dd,376) at witness_checkorder+0x593 Apr 7 20:16:35 new kernel: _mtx_lock_flags(c7898294,0,c07d43dd,376,c78888d4) at _mtx_lock_flags+0x67 Apr 7 20:16:35 new kernel: obj_alloc(c78888c0,1000,e32ffa2f,101,c78888d4) at obj_alloc+0x31 Apr 7 20:16:35 new kernel: slab_zalloc(c78888c0,1,c78888c0,c78888d4,1) at slab_zalloc+0x82 Apr 7 20:16:35 new kernel: uma_zone_slab(c78888c0,1,c78888d4,0,c07d43dd,68f) at uma_zone_slab+0xb5 Apr 7 20:16:35 new kernel: uma_zalloc_internal(c78888c0,0,1,c78888d4,0) at uma_zalloc_internal+0x28 Apr 7 20:16:35 new kernel: uma_zalloc_arg(c78888c0,0,1) at uma_zalloc_arg+0x2f8 Apr 7 20:16:35 new kernel: swp_pager_meta_build(c79446b4,38,0,2,0) at swp_pager_meta_build+0x108 Apr 7 20:16:36 new kernel: swap_pager_putpages(c79446b4,e32ffc00,4,0,e32ffb70) at swap_pager_putpages+0x2b4 Apr 7 20:16:36 new kernel: default_pager_putpages(c79446b4,e32ffc00,4,0,e32ffb70) at default_pager_putpages+0x18 Apr 7 20:16:36 new kernel: vm_pageout_flush(e32ffc00,4,0,0,e32ffbdc) at vm_pageout_flush+0x11e Apr 7 20:16:36 new kernel: vm_pageout_clean(c2c26308) at vm_pageout_clean+0x2a5 Apr 7 20:16:36 new kernel: vm_pageout_scan(0) at vm_pageout_scan+0x54b Apr 7 20:16:36 new kernel: vm_pageout(0,e32ffd48,0,c071cc3c,0) at vm_pageout+0x2d2 Apr 7 20:16:36 new kernel: fork_exit(c071cc3c,0,e32ffd48) at fork_exit+0xa8 Apr 7 20:16:36 new kernel: fork_trampoline() at fork_trampoline+0x8 Apr 7 20:16:36 new kernel: --- trap 0x1, eip = 0, esp = 0xe32ffd7c, ebp = 0 --- and then hundreds and thousands: Apr 7 20:20:29 new kernel: swap_pager_getswapspace(16): failed Apr 7 20:20:32 new last message repeated 44 times while actually there were 500MB of swap space left. What is going on? Regards, Artem From owner-freebsd-hardware@FreeBSD.ORG Wed Apr 7 12:49:09 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 6E84F16A4CE for ; Wed, 7 Apr 2004 12:49:09 -0700 (PDT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D4E343D39 for ; Wed, 7 Apr 2004 12:49:09 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 2767 invoked from network); 7 Apr 2004 19:47:04 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 7 Apr 2004 19:47:04 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i37JjkNF013535; Wed, 7 Apr 2004 15:46:43 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Wed, 7 Apr 2004 13:15:17 -0400 User-Agent: KMail/1.6 References: <4072AF32.9060506@npd.ufsc.br> <40736DD9.2090007@ec.rr.com> <4073FB4D.3060901@npd.ufsc.br> In-Reply-To: <4073FB4D.3060901@npd.ufsc.br> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404071315.17154.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: jason cc: Augusto Castelan Carlson Subject: Re: NICs not reconized - FreeBSD 4.9 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: Wed, 07 Apr 2004 19:49:09 -0000 On Wednesday 07 April 2004 08:59 am, Augusto Castelan Carlson wrote: > jason wrote: > >> What are the correct steps to install this realtek driver correctely? > >> And the broadcom 5788, can I make it work on FreeBSD 4.9? > > > > Did the default driver in bsd not work? I would not compile it in until > > I found one that worked. Just load and unload modules, it makes life > > easy. You could try to tweak the default driver to recgonize your card > > and it may just work. Since you downloaded the driver you could try > > looking at the differences between the web and system drivers with diff, > > it may be 95% the same. > > I suppose that there is no default driver for these NICs, as they are > not reconized during the system install. I know that they work on > FreeBSD 5.2.1, but the application that I'm intend to use only works on > version 4.x. > About loading and unload modules, I have to do that using > /boot/loader.conf or there is a command line to do it? > > It's not dangerous to tweak the code? Can I damage the NIC? Note that you can run 4.x binaries on a 5.x system so long as you install the compat4x distribution. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Wed Apr 7 14:28:52 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 967C516A4CE for ; Wed, 7 Apr 2004 14:28:52 -0700 (PDT) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71A0143D39 for ; Wed, 7 Apr 2004 14:28:52 -0700 (PDT) (envelope-from cjsantos@myrealbox.com) Received: from myrealbox.com cjsantos@smtp-send.myrealbox.com [81.84.196.183] $ on Novell NetWare via secured & encrypted transport (TLS); Wed, 07 Apr 2004 15:27:10 -0600 Message-ID: <40747223.7010008@myrealbox.com> Date: Wed, 07 Apr 2004 22:26:59 +0100 From: Carlos Jorge Santos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: pt, 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: D-Link DWL 520+ 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: Wed, 07 Apr 2004 21:28:52 -0000 Hi list, For what i've Googled there's currently no support for this Wireless Network Card, since it uses a Texas Instruments Chipset, and TI only supports Windoze. Are there any plans to get this NIC working under FreeBSD ? Thanks Carlos Santos Note : Unfortunately i've bought two of these cards today :( From owner-freebsd-hardware@FreeBSD.ORG Wed Apr 7 15:42:43 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 E7E2A16A4CE; Wed, 7 Apr 2004 15:42:43 -0700 (PDT) Received: from mail.npd.ufsc.br (mail.npd.ufsc.br [150.162.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E47B43D41; Wed, 7 Apr 2004 15:42:41 -0700 (PDT) (envelope-from carlson@npd.ufsc.br) Received: from localhost (localhost [127.0.0.1]) by mail.npd.ufsc.br (Postfix) with ESMTP id 90E649493; Wed, 7 Apr 2004 16:59:55 -0300 (EST) Received: from npd.ufsc.br (balantidium.interop.ufsc.br [150.162.248.5]) by mail.npd.ufsc.br (Postfix) with ESMTP id C395C9438; Wed, 7 Apr 2004 16:59:54 -0300 (EST) Message-ID: <40745DB7.9060202@npd.ufsc.br> Date: Wed, 07 Apr 2004 16:59:51 -0300 From: Augusto Castelan Carlson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <4072AF32.9060506@npd.ufsc.br> <40736DD9.2090007@ec.rr.com> <4073FB4D.3060901@npd.ufsc.br> <200404071315.17154.jhb@FreeBSD.org> In-Reply-To: <200404071315.17154.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS 0.3.12pre8 cc: freebsd-hardware@freebsd.org Subject: Re: NICs not reconized - FreeBSD 4.9 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: Wed, 07 Apr 2004 22:42:44 -0000 John Baldwin wrote: >> I know that they work on >>FreeBSD 5.2.1, but the application that I'm intend to use only works on >>version 4.x. > > Note that you can run 4.x binaries on a 5.x system so long as you install the > compat4x distribution. I'm using CoralReef from CAIDA. I compiled the application, and the kernel with ATM interface drivers. Can I get the ATM interface driver sources and add it to de FreeBSD 5.2.1 kernel compilation? It will be compatible? Can I copy CoralReef libs to FreeBSD 5.2.1 too? Thanks, Augusto From owner-freebsd-hardware@FreeBSD.ORG Wed Apr 7 16:13:23 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 4377816A4CE for ; Wed, 7 Apr 2004 16:13:23 -0700 (PDT) Received: from smtp2.linkline.com (smtp2.linkline.com [64.30.215.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19F4E43D31 for ; Wed, 7 Apr 2004 16:13:23 -0700 (PDT) (envelope-from sclements@linkline.com) Received: from samclementsde (host-66-59-225-129.lcinet.net [66.59.225.129]) by smtp2.linkline.com (Postfix) with ESMTP id 6193D109 for ; Wed, 7 Apr 2004 16:12:13 -0700 (PDT) From: "Samuel Clements" To: Date: Wed, 7 Apr 2004 16:12:16 -0700 Organization: linkLINE Communications, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 thread-index: AcQc9cRn0zwzSpjqQAm3/TkFGmQJbQ== Message-Id: <20040407231213.6193D109@smtp2.linkline.com> Subject: FreeBSD support for the SATA RAID controller on the Intel SE7210TP-E Server board X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: sclements@linkline.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Apr 2004 23:13:23 -0000 Greetings all, I am currently working with Intel trying to justify development of FreeBSD RAID Drivers for the SATA controller in the Intel SE7210TP-E (and S875WP1-E) Server Board which is not yet supported. I am looking for fellow Intel Premier Providers or Intel Product Dealers that have run into this particular incompatibility being a barrier to selling these otherwise excellent Server Boards, or people that would be selling to particular customers/into particular markets if this were available. I am trying to get an idea of market demand in the channel for this, then I can feed that back to Intel to see if they want the business or not. Please reply to me directly at sclements@linkline.com or reply to the list and I will contact you directly. Thanks for your time. Samuel Clements From owner-freebsd-hardware@FreeBSD.ORG Wed Apr 7 22:29:35 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 D3D8E16A4CE for ; Wed, 7 Apr 2004 22:29:35 -0700 (PDT) Received: from eterna.binary.net (eterna.binary.net [216.229.0.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A82C43D45 for ; Wed, 7 Apr 2004 22:29:35 -0700 (PDT) (envelope-from yura@binary.net) Received: from matrix.binary.net (matrix.binary.net [216.229.0.2]) by eterna.binary.net (Postfix) with ESMTP id E2031B439D for ; Thu, 8 Apr 2004 00:29:34 -0500 (CDT) Received: by matrix.binary.net (Postfix, from userid 100) id BA1D0102815; Thu, 8 Apr 2004 00:29:34 -0500 (CDT) Date: Thu, 8 Apr 2004 00:29:34 -0500 From: Yura Socolov To: freebsd-hardware@freebsd.org Message-ID: <20040408052934.GA82668@binary.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i Subject: VIA 8235 and 686 UDMA ICRC errors 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: Thu, 08 Apr 2004 05:29:35 -0000 Does anyone else have a problem lately with VIA-based motherboards and relatively big IDE harddrives? In particular, any combination of the following gives me a load of UDMA ICRC errors of various kinds, sometimes random panics (during boot or 20 minutes later), corrupted filesystems, etc. I have tried using two different 160G hard drives from two different vendors (maxtor and samsung), on three different, VIA-based motherboards of various age and from 3 different manufacturers (asus, shuttle, fic), using either VIA 686 or VIA 8235 chip, three different cables (so it's not a cable problem). DDR and PC133 memory as needed. FreeBSD versions from 5.2, to 5.2.1, -stable as of yesterday and about three weeks ago, and now compiling -current to check it out. If the drive is put in the BIOSPIO mode, everything works just dandy, including under heavy load on any of the boards. Under DMA100 i see ICRC errors as soon as there is more or less noticeable activity on the drive. For instance installing from CD causes an immediate error, installing from ftp at about 300 Kbytes/sec manages to survive, sometimes to the end of the minimalistic install process. If any of these drives are put in an amd64 box with FIC K8-800T (VIA 8237 chip), everything works flawlessly even under heavy load... I did see one similar bug report from last year in the non-urgent category, with no followups. Not sure if it's related, though, and I would call this more of a critical problem, since installation of FreeBSD on these kinds of systems is currently just not possible. Any pointers would be appreciated. Please cc: any replies to me, as i'm not on the list. Thank you for your time. -- Yura Socolov FP: A7192ABD96E15F5 19AB21E60C34109 -- http://users.binary.net/yura/ -- -- Opinions and views in this message are my own and my own only. -- -- "Two wrongs don't make a right... and three rights make a left." -- TRACON From owner-freebsd-hardware@FreeBSD.ORG Thu Apr 8 03:48: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 E6B8A16A4CE for ; Thu, 8 Apr 2004 03:48:00 -0700 (PDT) Received: from uplift.sunquest.com (uplift.hosp.misyshealthcare.com [149.138.10.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 972CC43D3F for ; Thu, 8 Apr 2004 03:47:55 -0700 (PDT) (envelope-from trf@uplift.sunquest.com) Received: from uplift.sunquest.com (localhost [127.0.0.1]) by uplift.sunquest.com (8.12.6/8.12.6) with ESMTP id i38Alp9V091211; Thu, 8 Apr 2004 03:47:51 -0700 (MST) (envelope-from trf@uplift.sunquest.com) Received: (from trf@localhost) by uplift.sunquest.com (8.12.6/8.12.6/Submit) id i38AloGB091210; Thu, 8 Apr 2004 03:47:50 -0700 (MST) Date: Thu, 8 Apr 2004 03:47:50 -0700 (MST) From: "Terry R. Friedrichsen" Message-Id: <200404081047.i38AloGB091210@uplift.sunquest.com> To: fbsd-hardware.z.yurasocolov@xoxy.net, freebsd-hardware@freebsd.org Subject: re: VIA 8235 and 686 UDMA ICRC errors 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: Thu, 08 Apr 2004 10:48:01 -0000 Yura wrote: > Does anyone else have a problem lately with VIA-based motherboards and > relatively big IDE harddrives? > [ ... ] > If the drive is put in the BIOSPIO mode, everything works just dandy, > including under heavy load on any of the boards. Under DMA100 i see > ICRC errors as soon as there is more or less noticeable activity on > the drive. FWIW, I observed the same thing with a pair of Western Digital WD1000BB 100 GB hard drives; when enough activity hit them, they'd get errors and drop into PIO mode, where they worked just fine. I replaced them with a pair of WD1200JB 120 GB drives (these are the special-edition version with 8 MB cache and maybe other differences as well) and had no problems. However, this was on an Asus A7M266-D dual-processor system with an AMD768 south bridge, running FreeBSD 4.7. Terry R. Friedrichsen terry@uplift.sunquest.com From owner-freebsd-hardware@FreeBSD.ORG Thu Apr 8 21:02:55 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 C923616A4CE for ; Thu, 8 Apr 2004 21:02:55 -0700 (PDT) Received: from venus.unixlabplus.com (h-67-100-145-26.nycmny83.covad.net [67.100.145.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CAE643D53 for ; Thu, 8 Apr 2004 21:02:52 -0700 (PDT) (envelope-from mwang@unixlabplus.com) Received: from venus.unixlabplus.com (localhost [127.0.0.1]) by venus.unixlabplus.com (8.12.5/8.12.5) with ESMTP id i39432P4003352; Fri, 9 Apr 2004 00:03:02 -0400 (EDT) Received: (from mwang@localhost) by venus.unixlabplus.com (8.12.5/8.12.5/Submit) id i3942uip003351; Fri, 9 Apr 2004 00:02:56 -0400 (EDT) Date: Fri, 9 Apr 2004 00:02:55 -0400 From: Michael Wang To: Bruce Evans Message-ID: <20040409040255.GA3318@unixlabplus.com> References: <20040407042821.GB1060@unixlabplus.com> <20040407222807.Y11144@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040407222807.Y11144@gamplex.bde.org> User-Agent: Mutt/1.4i cc: freebsd-hardware@FreeBSD.org Subject: Re: 4.9-R panic with Lava DSerial-PCI 3.3v and device puc 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: Fri, 09 Apr 2004 04:02:55 -0000 Bruce, Thank you very much for your earlier reply! Since I could not get the Lava DSerial-PCI 3.3v dual port serial card to work under 4.9-R. I upgraded the FreeBSD to 5.2.1-R. Here is the new info. (0) Hardware / Software info Hardware: - Dell 1750 - 133 MHz 3.3v PCIX - Lava DSerial-PCI 3.3v (dual serial port PCI adapter) Software: - FreeBSD 5.2.1-R - device puc (1) Boot message On 5.2.1-R, it did not panic (on 4.9-R, it paniced), The verbose boot message shows: ... pci3: on pcib2 pci3: physical bus=3 map[10]: type 4, range 32, base 0000ccf8, size 3, port disabled found-> vendor=0x1407, dev=0x0110, revid=0x00 bus=3, slot=6, func=0 class=07-00-02, hdrtype=0x00, mfdev=1 cmdreg=0x0040, statreg=0x0480, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[10]: type 4, range 32, base 0000ccf0, size 3, port disabled found-> vendor=0x1407, dev=0x0111, revid=0x00 bus=3, slot=6, func=1 class=07-00-02, hdrtype=0x00, mfdev=1 cmdreg=0x0040, statreg=0x0480, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 puc0: port 0xccf8-0xccff at device 6.0 on pci3 pcib2: matched entry for 3.6.INTA (source ) pcib2: device is hardwired to IRQ 24 puc0: failed to enable port mapping! puc0: could not get resource puc1: port 0xccf0-0xccf7 at device 6.1 on pci3 pcib2: matched entry for 3.6.INTA (source ) pcib2: device is hardwired to IRQ 24 puc1: failed to enable port mapping! puc1: could not get resource ... My reading is on pci3, it found two devices (two ports). Here are things that I doubt: (a) The "irq=255" does not look right. And later it says "device is hardwired to IRQ 24". (b) And I do not know why port disabled. (c) I also do not understand "size 3". The base address are 0000ccf0-0000ccf7 and 0000ccf8-0000ccff. The size should be 8, shouldn't it? On 4.9-R, the boot message is (I did not turn on verbose mode): pcib3: on motherboard pci3: on pcib3 pci3: (vendor=0x1407, dev=0x0110) at 6.0 irq 0 pci3: (vendor=0x1407, dev=0x0111) at 6.1 irq 0 And Bruce Evans said: irq 0 is from the card's PCI registers. The irq should be nonzero here. This is hard to recover from, and FreeBSD-4.9 apparently doesn't manage to figure out the actual irq. Look at BIOS boot messages to see if the BIOS prints a useable irq number. My guess is that it doesn't. (2) BIOS On Dell 1750, BIOS set IRQ for PCI device like this. You hit a "next key", the next IRQ appears. It is not continuously. In my case, it cycle through 5, 7, and 11. When you change the IRQ for one PCI device, the IRQ's for other devices change automatically. This is to avoid conflict. I set the IRQ for both ports to be 11 (they can not be different, they change together when you change one of them); no other PCI device has this IRQ. So I do not understand why this IRQ (11) is not picked up by FreeBSD. I tried other settings, there is no difference. (3) Vendor provided lavaconf.exe output The vendor provided a DOS utility "lavaconf.exe" on floppy. When I run it on DOS environment, I got: 330 Lava DSerial PCI port A = CCF8 331 Lava DSerial PCI port A = CCF0 The documentation says it should print the IRQ and memory address, but I do not know where the IRQ should be printed. I do not see a correct output. I do not know what 330 and 331 are. I recognized the memory address are the same as FreeBSD reported. When I downloaded the "lavaconf.exe" from lavalink website which is different than the one on floppy, I do not get any output when I run it. I would appreciate any advice what the possible problems are, and what should I try next. Thanks. PS: I am afraid I miss something from the boot message, it is included in its entirety here: pcib0: port 0xcf8-0xcff on acpi0 ---- initial configuration ------------------------ \\_SB_.LUSB irq 5: [ 4 5 6 7 10 11 12] low,level,sharable 0.15.0 ---- before setting priority for links ------------ ---- before fixup boot-disabled links ------------- ---- after fixup boot-disabled links -------------- ---- arbitrated configuration --------------------- \\_SB_.LUSB irq 5: [ 4 5 6 7 10 11 12] low,level,sharable 0.15.0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x1166, dev=0x0014, revid=0x33 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0014, revid=0x00 bus=0, slot=0, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0014, revid=0x00 bus=0, slot=0, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 32, base fd000000, size 24, enabled map[14]: type 4, range 32, base 0000ec00, size 8, enabled map[18]: type 1, range 32, base fe101000, size 12, enabled found-> vendor=0x1002, dev=0x4752, revid=0x27 bus=0, slot=14, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x00a7, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D1 D2 D3 current D0 found-> vendor=0x1166, dev=0x0201, revid=0x93 bus=0, slot=15, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0147, statreg=0x2200, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 4, range 32, base 000001f0, size 3, enabled map[14]: type 4, range 32, base 000003f4, size 2, enabled map[18]: type 4, range 32, base 00000170, size 3, enabled map[1c]: type 4, range 32, base 00000374, size 2, enabled map[20]: type 4, range 32, base 000008b0, size 4, enabled found-> vendor=0x1166, dev=0x0212, revid=0x93 bus=0, slot=15, func=1 class=01-01-8a, hdrtype=0x00, mfdev=1 cmdreg=0x0145, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 32, base fe100000, size 12, enabled pcib0: matched entry for 0.15.INTA (source \\_SB_.LUSB) pcib0: slot 15 INTA is routed to irq 5 found-> vendor=0x1166, dev=0x0220, revid=0x05 bus=0, slot=15, func=2 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0157, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x50 (20000 ns) intpin=a, irq=5 found-> vendor=0x1166, dev=0x0225, revid=0x00 bus=0, slot=15, func=3 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0110, revid=0x12 bus=0, slot=16, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0142, statreg=0x2230, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0110, revid=0x12 bus=0, slot=16, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0142, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0101, revid=0x05 bus=0, slot=17, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0142, statreg=0x2230, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0101, revid=0x05 bus=0, slot=17, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0142, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pci0: at device 14.0 (no driver attached) atapci0: port 0x8b0-0x8bf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 ata0: reset tp1 mask=03 ostat0=7f ostat1=7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0-slave: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: reset tp2 mask=00 stat0=ff stat1=ff devices=0x0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: simplex device, DMA on primary only ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1-master: stat=0x00 err=0x01 lsb=0x14 msb=0xeb ata1-slave: stat=0x00 err=0x00 lsb=0x00 msb=0xdf ata1: reset tp2 mask=03 stat0=00 stat1=00 devices=0x4 ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ohci0: mem 0xfe100000-0xfe100fff irq 5 at device 15.2 on pci0 ohci0: (New OHCI DeviceId=0x02201166) usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered isab0: at device 15.3 on pci0 isa0: on isab0 pcib1: on acpi0 ---- initial configuration ------------------------ ---- before setting priority for links ------------ ---- before fixup boot-disabled links ------------- ---- after fixup boot-disabled links -------------- ---- arbitrated configuration --------------------- pci4: on pcib1 pci4: physical bus=4 map[10]: type 4, range 32, base 0000bc00, size 8, enabled map[14]: type 1, range 64, base fcc30000, size 16, enabled map[1c]: type 1, range 64, base fcc20000, size 16, enabled pcib1: matched entry for 4.5.INTA (source ) pcib1: device is hardwired to IRQ 18 found-> vendor=0x1000, dev=0x0030, revid=0x07 bus=4, slot=5, func=0 class=01-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0117, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x48 (2160 ns), mingnt=0x11 (4250 ns), maxlat=0x12 (4500 ns) intpin=a, irq=18 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 4, range 32, base 0000b800, size 8, enabled map[14]: type 1, range 64, base fcc10000, size 16, enabled map[1c]: type 1, range 64, base fcc00000, size 16, enabled pcib1: matched entry for 4.5.INTB (source ) pcib1: device is hardwired to IRQ 19 found-> vendor=0x1000, dev=0x0030, revid=0x07 bus=4, slot=5, func=1 class=01-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0117, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x48 (2160 ns), mingnt=0x11 (4250 ns), maxlat=0x12 (4500 ns) intpin=b, irq=19 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit mpt0: port 0xbc00-0xbcff mem 0xfcc20000-0xfcc2ffff,0xfcc30000-0xfcc3ffff irq 18 at device 5.0 on pci4 mpt0: soft reset mpt1: port 0xb800-0xb8ff mem 0xfcc00000-0xfcc0ffff,0xfcc10000-0xfcc1ffff irq 19 at device 5.1 on pci4 mpt1: linking with peer (mpt0) mpt1: soft reset pcib2: on acpi0 ---- initial configuration ------------------------ ---- before setting priority for links ------------ ---- before fixup boot-disabled links ------------- ---- after fixup boot-disabled links -------------- ---- arbitrated configuration --------------------- pci3: on pcib2 pci3: physical bus=3 map[10]: type 4, range 32, base 0000ccf8, size 3, port disabled found-> vendor=0x1407, dev=0x0110, revid=0x00 bus=3, slot=6, func=0 class=07-00-02, hdrtype=0x00, mfdev=1 cmdreg=0x0040, statreg=0x0480, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[10]: type 4, range 32, base 0000ccf0, size 3, port disabled found-> vendor=0x1407, dev=0x0111, revid=0x00 bus=3, slot=6, func=1 class=07-00-02, hdrtype=0x00, mfdev=1 cmdreg=0x0040, statreg=0x0480, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 puc0: port 0xccf8-0xccff at device 6.0 on pci3 pcib2: matched entry for 3.6.INTA (source ) pcib2: device is hardwired to IRQ 24 puc0: failed to enable port mapping! puc0: could not get resource puc1: port 0xccf0-0xccf7 at device 6.1 on pci3 pcib2: matched entry for 3.6.INTA (source ) pcib2: device is hardwired to IRQ 24 puc1: failed to enable port mapping! puc1: could not get resource pcib3: on acpi0 ---- initial configuration ------------------------ ---- before setting priority for links ------------ ---- before fixup boot-disabled links ------------- ---- after fixup boot-disabled links -------------- ---- arbitrated configuration --------------------- pci2: on pcib3 pci2: physical bus=2 map[10]: type 1, range 64, base fcf30000, size 16, enabled map[18]: type 1, range 64, base fcf20000, size 16, enabled pcib3: matched entry for 2.0.INTA (source ) pcib3: device is hardwired to IRQ 16 found-> vendor=0x14e4, dev=0x1648, revid=0x02 bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0116, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=a, irq=16 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 64, base fcf10000, size 16, enabled map[18]: type 1, range 64, base fcf00000, size 16, enabled pcib3: matched entry for 2.0.INTB (source ) pcib3: device is hardwired to IRQ 17 found-> vendor=0x14e4, dev=0x1648, revid=0x02 bus=2, slot=0, func=1 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0116, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) intpin=b, irq=17 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit bge0: mem 0xfcf20000-0xfcf2ffff,0xfcf30000-0xfcf3ffff irq 16 at device 0.0 on pci2 bge0: Ethernet address: 00:0d:56:fd:d0:b3 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: bpf attached bge1: mem 0xfcf00000-0xfcf0ffff,0xfcf10000-0xfcf1ffff irq 17 at device 0.1 on pci2 bge1: Ethernet address: 00:0d:56:fd:d0:b4 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: bpf attached pcib4: on acpi0 ---- initial configuration ------------------------ ---- before setting priority for links ------------ ---- before fixup boot-disabled links ------------- ---- after fixup boot-disabled links -------------- ---- arbitrated configuration --------------------- pci1: on pcib4 pci1: physical bus=1 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 psm0: unable to allocate IRQ psmcpnp0 irq 12 on acpi0 psm0: current command byte:0065 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 sio0: irq maps: 0x2003 0x2013 0x2003 0x2003 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A acpi_cpu2: on acpi0 device_probe_and_attach: acpi_cpu2 attach returned 6 acpi_cpu2: on acpi0 device_probe_and_attach: acpi_cpu2 attach returned 6 ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it sio: sio0 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 ex_isa_identify() sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: