From owner-freebsd-i386@FreeBSD.ORG Sun Nov 26 21:51:28 2006 Return-Path: X-Original-To: freebsd-i386@hub.freebsd.org Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A5E216A560 for ; Sun, 26 Nov 2006 21:51:28 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id D722543FDA for ; Sun, 26 Nov 2006 21:49:29 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kAQLoGYV009472 for ; Sun, 26 Nov 2006 21:50:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kAQLoGTV009471; Sun, 26 Nov 2006 21:50:16 GMT (envelope-from gnats) Date: Sun, 26 Nov 2006 21:50:16 GMT Message-Id: <200611262150.kAQLoGTV009471@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Marcel Moolenaar Cc: Subject: Re: i386/105616: UART PCI device just silent... X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marcel Moolenaar List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2006 21:51:28 -0000 The following reply was made to PR i386/105616; it has been noted by GNATS. From: Marcel Moolenaar To: Helge Oldach Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: i386/105616: UART PCI device just silent... Date: Sun, 26 Nov 2006 13:35:51 -0800 On Nov 21, 2006, at 12:20 PM, Helge Oldach wrote: > Would you kindly advice on how to proceed? Hi Helge, I'm still trying to understand what the failure mode is and what may cause it, so at this time I'm still looking for answers. Please bear with me... I'll try to get one of those cards myself. That should help solve this. See below. > The "sysctl dev" delta between a "sio kernel" and an "uart kernel" is: > > 107,124c107,118 > < dev.sio.4.%desc: Dolphin Peripherals 4036 > < dev.sio.4.%driver: sio > < dev.sio.4.%parent: puc0 > < dev.sio.5.%desc: Dolphin Peripherals 4036 > < dev.sio.5.%driver: sio > < dev.sio.5.%parent: puc0 > < dev.sio.0.%desc: Standard PC COM port > < dev.sio.0.%driver: sio > < dev.sio.0.%location: handle=\_SB_.PCI0.IBRG.COM1 > < dev.sio.0.%pnpinfo: _HID=PNP0501 _UID=1 > < dev.sio.0.%parent: acpi0 > < dev.sio.0.wake: 0 > < dev.sio.1.%desc: Standard PC COM port > < dev.sio.1.%driver: sio > < dev.sio.1.%location: handle=\_SB_.PCI0.IBRG.COM2 > < dev.sio.1.%pnpinfo: _HID=PNP0501 _UID=2 > < dev.sio.1.%parent: acpi0 > < dev.sio.1.wake: 0 > --- >> dev.uart.2.%desc: 16550 or compatible >> dev.uart.2.%driver: uart >> dev.uart.2.%parent: puc0 >> dev.uart.3.%desc: 16550 or compatible >> dev.uart.3.%driver: uart >> dev.uart.3.%parent: puc0 >> dev.uart.0.%desc: 16550 or compatible >> dev.uart.0.%driver: uart >> dev.uart.0.%parent: isa0 >> dev.uart.1.%desc: 16550 or compatible >> dev.uart.1.%driver: uart >> dev.uart.1.%parent: isa0 > > Maybe this gives some hint? One thing that strikes me as odd is that sio(4) attaches to acpi(4), while uart(4) attaches to isa(4). You mentioned that the kernels where otherwise identical, but that you had to update device.hints. I would expect uart(4) to attach to acpi(4) and not to isa(4). While this has nothing to do with puc(4), I'd like to know why this is happening. Could you send me a verbose dmesg of both kernels? thanks, -- Marcel Moolenaar xcllnt@mac.com