From owner-freebsd-hardware@FreeBSD.ORG Sat Apr 10 06:44:34 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 4558316A4CE for ; Sat, 10 Apr 2004 06:44:34 -0700 (PDT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 902F943D48 for ; Sat, 10 Apr 2004 06:44:33 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])i3ADiV5v016307; Sat, 10 Apr 2004 23:44:31 +1000 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i3ADiTGQ031824; Sat, 10 Apr 2004 23:44:30 +1000 Date: Sat, 10 Apr 2004 23:44:28 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Michael Wang In-Reply-To: <20040409040255.GA3318@unixlabplus.com> Message-ID: <20040410230659.T25530@gamplex.bde.org> References: <20040407042821.GB1060@unixlabplus.com> <20040407222807.Y11144@gamplex.bde.org> <20040409040255.GA3318@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: Sat, 10 Apr 2004 13:44:34 -0000 On Fri, 9 Apr 2004, Michael Wang wrote: > 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. Looks like the interrupt configuration is still broken. Yesterday's changes to pci configuration may help. [... many details deleted. Reply to the original if you have more comments on it.] > (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". I think 255 is the correct value for "irq not there" (not sure). I don't understand the hardwired part. > (b) And I do not know why port disabled. The port enable bit is read from the devices's pci registers like the irq value, and it is not set. So the BIOS is apparently disabling the device. > (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? The size is in bits: 2^3 = 8. Bruce