From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 9 18:23:02 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5CFD116A402 for ; Fri, 9 Feb 2007 18:23:02 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: from smtp102.sbc.mail.mud.yahoo.com (smtp102.sbc.mail.mud.yahoo.com [68.142.198.201]) by mx1.freebsd.org (Postfix) with SMTP id 1303513C491 for ; Fri, 9 Feb 2007 18:23:01 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: (qmail 54686 invoked from network); 9 Feb 2007 18:23:01 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=FUmbc8bnJcI0FNTsZBlnFI6d2D79mmSPR01Qc/NpujcCqYEYlY6Am6Ph6aXoLAVo+3mQWvt0ieZvi8QnxAuWOcWmoY6NabKdNi5j6IqtOXw8N939xttNukcXrEo0upO3nlSRveyWstGOSwchowExPfHtF1Wy/mvE1X2teVp7igY= ; Received: from unknown (HELO ?192.168.0.190?) (dr2867.business@pacbell.net@71.146.10.137 with plain) by smtp102.sbc.mail.mud.yahoo.com with SMTP; 9 Feb 2007 18:23:01 -0000 X-YMail-OSG: WLnqwXUVM1mmWSWA7jaTAJ1hmQcmr9bJbl50V.nLfFo3XBh0fDJhOcrXWihf4yHdXmD3Q5j90I3AxMmugKMw88r_gM840qK3wRsBMZDdmChdJPfEzGddZEfcg0XvCnhiXUhSUUwF_8P04FY- Message-ID: <45CCBCFB.4020402@pacbell.net> Date: Fri, 09 Feb 2007 10:27:07 -0800 From: Daniel Rudy User-Agent: Mozilla/5.0 (X11R6; UNIX; FreeBSD/i386 6.1-RELEASE-p7; en-US; ja-JP; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: Peter Jeremy References: <45CC2DDF.6040600@pacbell.net> <20070209110522.GF834@turion.vk2pj.dyndns.org> In-Reply-To: <20070209110522.GF834@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, wb@freebie.xs4all.nl Subject: Re: PING: Someone on the core team. (Modem Problem) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 18:23:02 -0000 At about the time of 2/9/2007 3:05 AM, Peter Jeremy stated the following: > I'm not on the core team but I'm not sure why you believe that > this has anything to do with core. > This very much does involve core because I plan on handing the modem, and the entire computer if necessary, over to a core developer so they can figure out why it doesn't work and correct the problem, if they can. I am serious about getting this issue resolved because I'm under the gun myself. Furthermore, I don't have nearly the required knowledge of how the kernel does things to even attempt to resolve the issue on my own. > On 2007-Feb-09 00:16:31 -0800, Daniel Rudy wrote: >> sio0: configured irq 19 not in bitmap of probed irqs 0 >> sio0: port may not be enabled >> sio0: port >> 0xdc00-0xdcff,0xe000-0xe0ff,0xe400-0xe407 mem 0xeb107000-0xeb1070ff >> irq 19 at device 11.0 on pci0 >> sio0: type 16550A > > Is this device visible in the BIOS and if so, what does the BIOS > say its configuration is. The dmesg from a verbose boot may be > useful. The "port may not be enabled" line looks to be the most > relevant one. The modem is PCI, and there is no facility in the BIOS to display what cards are in the system. Furthermore, the irq mapping shows irq 3-15, irq 17, 18, and 19 do not show on the list. Below is the full dmesg from the boot: Copyright (c) 1992-2007 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 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Sempron(tm) 2400+ (1662.51-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x681 Stepping = 1 Features=0x383fbff AMD Features=0xc0480800 real memory = 100597760 (95 MB) avail memory = 88645632 (84 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff,0x480-0x48f,0x1000-0x10df,0x10e0-0x10ff on acpi0 pci0: on pcib0 agp0: mem 0xe8000000-0xe9ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x4000-0x400f at device 2.5 on pci0 ata0: on atapci0 ata1: on atapci0 ohci0: mem 0xeb104000-0xeb104fff irq 20 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xeb100000-0xeb100fff irq 21 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xeb101000-0xeb101fff irq 22 at device 3.2 on pci0 ohci2: [GIANT-LOCKED] usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xeb102000-0xeb102fff irq 23 at device 3.3 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 8 ports with 8 removable, self powered sis0: port 0xd000-0xd0ff mem 0xeb103000-0xeb103fff irq 19 at device 4.0 on pci0 miibus0: on sis0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:14:2a:54:65:ad sis1: port 0xd400-0xd4ff mem 0xeb105000-0xeb105fff irq 17 at device 9.0 on p ci0 sis1: Silicon Revision: DP83816A miibus1: on sis1 ukphy0: on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis1: Ethernet address: 00:0f:b5:44:9f:4b sis2: port 0xd800-0xd8ff mem 0xeb106000-0xeb106fff irq 18 at device 10.0 on pci0 sis2: Silicon Revision: DP83816A miibus2: on sis2 ukphy1: on miibus2 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis2: Ethernet address: 00:0f:b5:46:99:c2 sio0: configured irq 19 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: port 0xdc00-0xdcff,0xe000-0xe0ff,0xe400-0xe407 mem 0xeb107000-0xeb1070ff irq 19 at device 11.0 on pci0 sio0: type 16550A acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x60,0x64 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 Generic PS/2 mouse, device ID 0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1662506085 Hz quality 800 Timecounters tick every 1.000 msec ad0: 38166MB at ata0-master UDMA100 acd0: CDROM at ata1-slave UDMA33 Trying to mount root from ufs:/dev/ad0s1a >> I have no idea WHY it's saying IRQ 19 as IRQ 19 is used by sis0. > > Interrupts on the PCI bus can be shared and quite often are. > And FreeBSD doesn't support shared interrupts, right? (At least that used to be the case, not sure about now). If it does allow irq sharing, then why isn't it working? And if it doesn't support irq sharing, then why is FreeBSD assigning 2 devices to the same irq to begin with? >> Now I know that device says WinModem, but this is most definitely *NOT* >> a WinModem. > > It appears that there is an error in /usr/share/misc/pci_vendors. Feel > free to write a bug report. The kernel is correctly recognizing it. > >> Here's the problem. Anything that this modem outputs, requires multiple >> inputs for it to read out on the screen. Here's an example: >> >> gateway# cu -l /dev/cuad0 -s 57600 >> Connected >> at&v >> >> Option Selection AT Cmd >> --------------- ------------ -------- > ... > > So it _does_ work. > >> In order to get that output, I have to hit either enter or space 61 >> times (yes sixty-one is not a typo) to get it. When it prints, it only >> prints out about 16 characters at a time (which happens to be the size >> of the FIFO buffer in a generic 16550A UART). > > Probably because the interrupts are not working. > >> As to why FreeBSD is assigning two devices to the same IRQ I have no >> idea, especially since there are plenty of IRQs available that can be >> used (serial, parallel are turned off in the BIOS). > > Probably because your motherboard vendor decided to save a few deci- > cents by not bothering to connect up all the available interrupt > inputs and just share one. This isn't FreeBSD - it's the copper > tracks on your motherboard. > Its kinda strange though if that was the case, the other cards wouldn't work then because they would all be sharing the same irq. The 3 network interfaces are assigned 17, 18, and 19. sis0 is on the mainboard, sis1 and sis2 are add-in cards on the pci bus. -- Daniel Rudy