From owner-freebsd-questions@FreeBSD.ORG Sat Apr 1 20:27:20 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7108916A401 for ; Sat, 1 Apr 2006 20:27:20 +0000 (UTC) (envelope-from duncan.fbsd@gmail.com) Received: from smtp105.sbc.mail.re2.yahoo.com (smtp105.sbc.mail.re2.yahoo.com [68.142.229.100]) by mx1.FreeBSD.org (Postfix) with SMTP id C272B43D49 for ; Sat, 1 Apr 2006 20:27:18 +0000 (GMT) (envelope-from duncan.fbsd@gmail.com) Received: (qmail 29380 invoked from network); 1 Apr 2006 20:27:18 -0000 Received: from unknown (HELO pres1750.airedalesrule.homeunix.org) (donaldj@ameritech.net@69.212.204.41 with plain) by smtp105.sbc.mail.re2.yahoo.com with SMTP; 1 Apr 2006 20:27:18 -0000 From: "Donald J. O'Neill" To: Peter Date: Sat, 1 Apr 2006 14:27:09 -0600 User-Agent: KMail/1.9.1 References: <20060401035903.88421.qmail@web60013.mail.yahoo.com> In-Reply-To: <20060401035903.88421.qmail@web60013.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604011427.09206.duncan.fbsd@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: ACPI disables network (why?) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Apr 2006 20:27:20 -0000 On Friday 31 March 2006 21:59, Peter wrote: > Here is what I have for "irq". It looks like irq 22 is being > overused. > > $ dmesg | grep irq > ioapic0 irqs 0-23 on motherboard > ohci0: mem 0xfc003000-0xfc003fff irq > 22 at device 2.0 on pci0 > ohci1: mem 0xfc004000-0xfc004fff irq > 21 at device 2.1 on pci0 > ehci0: mem 0xfc005000-0xfc0050ff > irq 20 at device 2.2 on pci0 > pcm0: port 0xe000-0xe07f,0xdc00-0xdcff mem > 0xfc001000-0xfc001fff irq 22 at device 6.0 on pci0 > nvidia0: mem > 0xe0000000-0xefffffff,0xf8000000-0xf8ffffff irq 16 at device 0.0 on > pci1 > skc0: port 0xc000-0xc0ff mem > 0xfb000000-0xfb003fff irq 19 at device 11.0 on pci2 > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on > acpi0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 > on acpi0 > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > ppc0: port 0x378-0x37f irq 7 on > acpi0 atkbdc0: port 0x64,0x60 irq 1 on > acpi0 atkbd0: irq 1 on atkbdc0 > > __________________________________________________ Not necessarily, I counted two uses. On one of my computers, irq 19 is used 4 times. There's only so many irq's available, sometimes some of them are shared. The problem is when some devices don't want to share. Do 'dmesg | grep storm', and 'dmesg | grep throt' that will tell you what irq has the problem and something is being shutdown. Then you can do 'dmesg | grep ' to find what devices are using that irq and determine what to do. With my computers I have found a bad usb mouse (dam' microsloth product, should have known better), some devices that couldn't be plugged into the usb2.0 ports I have, they had to be plugged into usb1.1 ports only, a modem that I thought was shot but would work like a champ by repositioning it on the pci bus, and some NICs that would work best by repositioning. I also found out, what FreeBSD likes, Windows XP doesn't necessarily like. After I got everything straightened around for FreeBSD-STABLE, Windows XP took a 1/2 hour to come up, booting up with the XP install disc took about the same. It still did it after a fresh install of XP. so, I told my wife: "Windows is shot, Microsoft wans me to call them to get a new number which won't help. You don't do anything on Windows that you can't do as well as or better on FreeBSD. I can't tell exactly what's wrong, Microsoft doesn't want me to know, FreeBSD thinks I want to know. I'm pulling the plug on windows and their money grubbing ways. By the way, I do give FreeBSD lessons, but pay attention or you'll have to learn on your own." Yeah, one less Windows XP installation to worry about. Of course, I didn't figure out a reason (for myself) for what was happening with Windows XP till later. You're probably going to have to put your NIC in a different slot. Don