Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Jul 2004 09:03:34 -0600
From:      Scott Long <scottl@samsco.org>
To:        "Jordan K. Hubbard" <jkh@queasyweasel.com>
Cc:        freebsd-scsi@freebsd.org
Subject:   Re: ahc driver now borked in -current?
Message-ID:  <40F7EE46.5040701@samsco.org>
In-Reply-To: <1AC4B82A-D71A-11D8-8D2E-000393BB9222@queasyweasel.com>
References:  <49011D34-D2BB-11D8-81E2-000393BB9222@queasyweasel.com> <40F157C2.8010400@samsco.org> <1AC4B82A-D71A-11D8-8D2E-000393BB9222@queasyweasel.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Jordan K. Hubbard wrote:
> Interestingly enough, the same kernel boots in 'safe mode', so one of 
> the canned safeboot settings must be causing this to work.  It's clearly 
> not the ACPI one, however, since I tried disabling that one 
> independently and things were still hosed.
> 
> - Jordan
> 
> On Jul 11, 2004, at 8:07 AM, Scott Long wrote:
> 
>> Having the dump card state message will be really useful.  You might
>> want to examine the message and see if mentions anything about
>> interrupts not working, or 'SCB already completed'.
>>
> -- 
> Jordan K. Hubbard
> Engineering Manager, BSD technology group
> Apple Computer
> 

Safe mode disables the following:

ACPI
APIC (and by extention, SMP)
ATA DMA
ATAPI DMA
ATA WC
EISA

My guess is that disabling the APIC is doing the trick for you.
It's strange that ACPI doesn't make a difference; usually when
it comes to interrupt routing, either the mptable or ACPI are
hosed, but not both.  This wouldn't happen to be a Dell
workstation, would it?  I had a very similar problem with my
Dell, and wound up having to hard-code some of the routing.

At this point I'd recommend contacting John Baldwin.

Scott


Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40F7EE46.5040701>