From owner-freebsd-stable@FreeBSD.ORG Tue Apr 15 00:17:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82E6B37B401 for ; Tue, 15 Apr 2003 00:17:00 -0700 (PDT) Received: from chapel-hill.tfd.com (hnllhi1-ar3-4-3-111-082.hnllhi1.dsl-verizon.net [4.3.111.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9447D43FAF for ; Tue, 15 Apr 2003 00:16:59 -0700 (PDT) (envelope-from kent.hauser@verizon.net) Received: from localhost (localhost [127.0.0.1]) by chapel-hill.tfd.com (8.12.9/8.12.9) with ESMTP id h3F7GwTU001429 for ; Mon, 14 Apr 2003 21:16:59 -1000 (HST) (envelope-from kent.hauser@verizon.net) From: Kent Hauser To: stable@freebsd.org Date: Mon, 14 Apr 2003 21:16:57 -1000 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200304142116.57726.kent.hauser@verizon.net> Subject: NVIDIA driver / internal modem irq conflict X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2003 07:17:00 -0000 Hi, I'm having trouble with an IRQ conflict I can't figure out how to resolve. I tried KDE (which is great), but this required the NVIDIA driver. However, this driver conflicts with my modem. If the driver is loaded, then the system locks up when accessing the modem. If I remove the NVIDIA driver from /boot/loader.conf, modem works fine. I tried moving the modem to different slots, but no joy. (The modem likes the slot it's in, but not the others.) Any help would be appreciated. System running 4.8-STABLE with X11 & NVidia built within last week. (4.8-STABLE #2: Mon Apr 14 07:42:46 HST 2003) Kernel probe info w/o NVIDIA (modem works): at boot prompt enter: > unload all > load kernel > load snd_emu10k > boot Apr 14 09:30:27 chapel-hill /kernel: pci1: on pcib1 Apr 14 09:30:27 chapel-hill /kernel: pci1: at 0.0 irq 11 Apr 14 09:30:27 chapel-hill /kernel: sio0: <3COM PCI FaxModem> port 0x1428-0x142f irq 11 at device 14.0 on pci0 Apr 14 09:30:27 chapel-hill /kernel: sio0: moving to sio2 Apr 14 09:30:27 chapel-hill /kernel: sio2: type 16550A Apr 14 09:30:27 chapel-hill /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Apr 14 09:30:27 chapel-hill /kernel: sio0: type 16550A Apr 14 09:30:27 chapel-hill /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Apr 14 09:30:27 chapel-hill /kernel: sio1: type 16550A ========== Kernel probe info with NVIDIA (system locks up then modem accessed): Method: just let it boot and load the nvidia.ko module: Apr 14 09:32:26 chapel-hill /kernel: Preloaded elf module "agp.ko" at 0xc06b9280. Apr 14 09:32:26 chapel-hill /kernel: Preloaded elf module "nvidia.ko" at 0xc06b931c. Apr 14 09:32:26 chapel-hill /kernel: pci1: on pcib1 Apr 14 09:32:26 chapel-hill /kernel: nvidia0: mem 0xfc000000-0xfdffffff,0xf5000000-0xf5ffffff irq 11 at device 0.0 on pci1 Apr 14 09:32:26 chapel-hill /kernel: sio0: <3COM PCI FaxModem> port 0x1428-0x142f irq 11 at device 14.0 on pci0 Apr 14 09:32:26 chapel-hill /kernel: sio0: moving to sio2 Apr 14 09:32:26 chapel-hill /kernel: sio2: type 16550A Apr 14 09:32:26 chapel-hill /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Apr 14 09:32:26 chapel-hill /kernel: sio0: type 16550A Apr 14 09:32:26 chapel-hill /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Apr 14 09:32:26 chapel-hill /kernel: sio1: type 16550A =========