From owner-freebsd-current Wed Oct 2 9:42:57 2002 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 4C38B37B401; Wed, 2 Oct 2002 09:42:56 -0700 (PDT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74F0C43E6E; Wed, 2 Oct 2002 09:42:55 -0700 (PDT) (envelope-from mark@grimreaper.grondar.org) Received: from storm.FreeBSD.org.uk (uucp@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.12.5/8.12.5) with ESMTP id g92Ggsrp037601; Wed, 2 Oct 2002 17:42:54 +0100 (BST) (envelope-from mark@grimreaper.grondar.org) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.12.5/8.12.5/Submit) with UUCP id g92GgsXU037600; Wed, 2 Oct 2002 17:42:54 +0100 (BST) Received: from grimreaper.grondar.org (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.6/8.12.5) with ESMTP id g92Ge6eO005337; Wed, 2 Oct 2002 17:40:06 +0100 (BST) (envelope-from mark@grimreaper.grondar.org) Message-Id: <200210021640.g92Ge6eO005337@grimreaper.grondar.org> To: John Baldwin Cc: current@FreeBSD.org Subject: Re: PCI brokenness References: In-Reply-To: ; from John Baldwin "Wed, 02 Oct 2002 12:34:04 EDT." Date: Wed, 02 Oct 2002 17:40:06 +0100 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >> So it doesn't boot at all, that's different from "hard-hang during reboot". > >> :) After ppc your device probe is over. You could be getting an > >> interrupt storm. Can you break into ddb when this happens? > > > > Roger the diference. :-) > > > > No. I cannot break into DDB. The keyboard may as well not be there. > > Humm. :( This is definitely a regression that needs to be fixed. > (For the non-ACPI case). Did you have this problem on older kernels > as well? Does 4.x work ok w/o hanging? I'll check. The current problems are on my laptop, and I cannot afford the trauma that reverting it to RELENG_4 will cause. I have a crash box at home that I'll try. > >> > In practical terms, this is a regression, in that previous function > >> > has been removed before an adequate replacement was ready. > >> > >> Ok, I have a question now. How did ata get probed before? If you > >> add hints for it does it get probed? It doesn't appear to be a PCI > >> device. It may be that we need to make it work as an ATA attachment > >> somehow. Also, did ata1 show up before? > > > > Yes - I have hints. > > > > Here is my hints file (which has not changed in at least 6 months) > > Ok, so you only have ata0 and no ata1. So that means the ACPI ata > attachment almost worked. Humm, try doing a hack to change ATA_IOADDR_RID > in ata-all.h from 0 to 1 along with the previous patch to add an acpi > attachment for ata and see if that works. I still have no idea why > the ata hint device isn't working. It should be working fine. :( OK. I'll get back to you shortly. M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message