From owner-freebsd-current@FreeBSD.ORG Fri Feb 13 04:44:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5495D16A4CE; Fri, 13 Feb 2004 04:44:10 -0800 (PST) Received: from fisk.demonized.net (h97n2fls33o834.telia.com [213.66.186.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id C52B843D1D; Fri, 13 Feb 2004 04:44:09 -0800 (PST) (envelope-from manlix@demonized.net) Received: from beard.demonized.net (beard.demonized.net [172.22.1.2]) by fisk.demonized.net (8.12.10/8.12.10) with SMTP id i1DCi73d000213; Fri, 13 Feb 2004 13:44:07 +0100 (CET) (envelope-from manlix@demonized.net) Date: Fri, 13 Feb 2004 13:44:02 +0100 From: Johan Pettersson To: freebsd-current@freebsd.org Message-Id: <20040213134402.4c03072e.manlix@demonized.net> X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: Alexander@Leidinger.net cc: pilkis@gmx.net cc: kris@obsecurity.org Subject: Re: Bad interrupt routing causes my SATA controller to fail. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 12:44:10 -0000 Hmm, this really confuses me. At the boot prompt I did a unload kernel and then load kernel. It booted up with HTT, acpi and apic enabled and working. I got these messages on ad4: ad4: TIMEOUT - READ_DMA retrying (2 retries left) LBA=1 ad4: timeout sending command=c8 ad4: error issuing DMA command but, it didnt hang there as usual. I thought it maybe was something with the kernel modules loaded. /boot/loader.conf hw.ata.atapi_dma=1 if_sk_load="YES" linux_load="YES" vesa_load="YES" #agp_load="YES" snd_emu10k1_load="YES" uhid_load="YES" ums_load="YES" #nvidia_load="YES" When doing unload kernel they are unloaded. So I commented them out in loader.conf and rebooted. Now no modules is loaded. But, it hangs on ad4 when booting up withoit doing an unload kernel and then load kernel. So I rebooted, did an unload kernel and then load kernel. Worked just fine to boot up with HTT, acpi and apic enabled. Did a sysctl debug.bootverbose=1. No messages printed at the console. Then I loaded the if_sk.ko module. Tons of ata3: spurious interrupt - status=0x7f error=0xff messages printed at the console. Unloaded if_sk.ko and got a kernel panic. I don't know what it is but to me it looks very strange. Whats happening when doing unload kernel and then load kernel that gets it to boot up with HTT, acpi and apic enabled and not hang on ad4?