Date: Tue, 4 Jan 2005 10:06:12 -0500 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-acpi@FreeBSD.org Subject: Re: ACPI + SMBus disables ISA bus Message-ID: <200501041006.12235.jhb@FreeBSD.org> In-Reply-To: <20050103222556.GW79646@cirb503493.alcatel.com.au> References: <20050103222556.GW79646@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 03 January 2005 05:25 pm, Peter Jeremy wrote: > I originally sent this to -stable but have received no response. It's > possible that it's an ACPI problem so I'm trying here. > > I'm trying to upgrade a system from 4.10 to 5.3p2 and am running into > problems with the ISA bus disappearing (not probing or attaching) when > I have both ACPI and SMBus enabled. This leads to a panic when > something tries to do a sysctl on the (non-existent) console. > > The problem is masked if I use a serial console because the only ISA > device I need is the VGA adapter and the lack of vga0 and syscons > doesn't worry the serial console. > > I've had a google around and it looks like this combination should work. > At least, I can't find anything forbidding it and can find some dmesgs > showing both ACPI and SMBus. > > The relevant sections of a GENERIC "boot -v" shows: > ... > AcpiOsDerivePciId: bus 0 dev 17 func 0 > AcpiOsDerivePciId: bus 0 dev 17 func 0 > ... > found-> vendor=0x1106, dev=0x3147, revid=0x00 > bus=0, slot=17, func=0 > class=06-01-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0087, statreg=0x0210, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > powerspec 2 supports D0 D3 current D0 > map[20]: type 4, range 32, base 0000fc00, size 4, enabled > ... > pci1: <display, VGA> at device 0.0 (no driver attached) > pci0: <multimedia, audio> at device 8.0 (no driver attached) > pci0: <multimedia> at device 11.0 (no driver attached) > isab0: <PCI-ISA bridge> at device 17.0 on pci0 > isa0: <ISA bus> on isab0 > atapci0: <VIA 8233A UDMA133 controller> port > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 > > If I add the following options to GENERIC: > device smbus > device viapm > device smb > device iicbb > device iicbus > then the ISA bus vanishes and the above probe messages change to: > ... > pci1: <display, VGA> at device 0.0 (no driver attached) > pci0: <multimedia, audio> at device 8.0 (no driver attached) > pci0: <multimedia> at device 11.0 (no driver attached) > viapropm0: SMBus I/O base at 0x400 > viapropm0: <VIA VT8233 Power Management Unit> port 0x400-0x40f at device > 17.0 on pci0 viapropm0: SMBus revision code 0x0 > smbus0: <System Management Bus> on viapropm0 > smb0: <SMBus generic I/O> on smbus0 > atapci0: <VIA 8233A UDMA133 controller> port > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 > > I can't get ACPI running properly in 4.x but I can have both SMBus and ACPI > loaded and dmesg shows: > ... > viapropm0: SMBus I/O base at 0x400 > viapropm0: <VIA VT8233 Power Management Unit> port 0x400-0x40f at device > 17.0 on pci0 viapropm0: SMBus revision code 0x0 > smb0: <SMBus general purpose I/O> on smbus0 > ... > isa0: <ISA bus> on motherboard > > The motherboard is a Gigabyte GA-7VRXP with F12 BIOS (the latest AFAIK). > Switching between PIC and APIC modes in the BIOS has no effect. There's > no explicit "PnP/nonPnP" option. > > Should this work? If so, where should I look for clues as to why it > doesn't for me? It should work, but the problem is that the viapropm0 device needs to create an isab0 child as well, or perhaps it should be an isab driver and it should have both isa and smbus children devices. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501041006.12235.jhb>