From owner-freebsd-bugs@FreeBSD.ORG Tue Feb 10 06:50:21 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 576D216A4CE for ; Tue, 10 Feb 2004 06:50:21 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A8B643D1D for ; Tue, 10 Feb 2004 06:50:21 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i1AEoKbv077107 for ; Tue, 10 Feb 2004 06:50:20 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i1AEoKIb077106; Tue, 10 Feb 2004 06:50:20 -0800 (PST) (envelope-from gnats) Date: Tue, 10 Feb 2004 06:50:20 -0800 (PST) Message-Id: <200402101450.i1AEoKIb077106@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Bruce Evans Subject: Re: kern/60226: ichsmb driver doesn't detects SMB bus on Asus P4B533/P4PE motherboards X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bruce Evans List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2004 14:50:21 -0000 The following reply was made to PR kern/60226; it has been noted by GNATS. From: Bruce Evans To: Alexander Zagrebin Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/60226: ichsmb driver doesn't detects SMB bus on Asus P4B533/P4PE motherboards Date: Wed, 11 Feb 2004 01:44:56 +1100 (EST) On Tue, 10 Feb 2004, Alexander Zagrebin wrote: > I successfully applied this patch to RELENG_5_2, > but there was the compile error at fixup_pci.c. > The problem was solved after adding line "#include " to > it. > With new kernel SMBus was detected and seems to be working. > But, smbus got irq4 and i lost my sio0. :( > > ... > Feb 9 20:59:12 bsd kernel: [-] pmccfg: 49 > Feb 9 20:59:12 bsd kernel: Enabled Intel 801SMBus > Feb 9 20:59:12 bsd kernel: pci_cfgintr: 0:31 INTA BIOS irq 9 > Feb 9 20:59:12 bsd kernel: pci_cfgintr: 0:31 INTB BIOS irq 9 > ... > Feb 9 20:59:12 bsd kernel: ichsmb0: > port 0xe800-0xe81f at device 31.3 on pci0 > Feb 9 20:59:12 bsd kernel: pci_cfgintr: 0:31 INTB routed to irq 4 > ^^^^^^^^^^^^^^^^^^^^ sio0 on irq4 should still work. > Feb 9 20:59:12 bsd kernel: smbus0: on ichsmb0 > Feb 9 20:59:12 bsd kernel: smb0: on smbus0 > ... > Feb 9 20:59:12 bsd kernel: sio0: configured irq 4 not in bitmap of probed > irqs 0 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > ^^^^^ This message can be ignored if you know that irq 4 is correct. Old versions used to fail here, but that is not quite right because it is possible for the irq to work despite the test for it failing here. > Feb 9 20:59:12 bsd kernel: sio0: port may not be enabled This message is just a normally-usless hint about why the previous message was printed. > Feb 9 20:59:12 bsd kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on > isa0 Since you didn't get the message "sio0: unable to activate interrupt in fast mode - using normal mode", sio0 has apparently been attached first and subsequent attachment of ichsmb should fail because sio has set up the interrupt in fast mode so it is unavailable in the normal mode that ichsmb wants. If it actually succeeds, then there is a bug in the interrupt attachment (larger than the unimplemented details that prevent changing the sio interrupt's mode after attach time), and the bug could easily break delivery of interrupts too. Things should work better if ichsmb is attached first. I don't know how to force this except by making sio a module. Bruce