From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: libata machine check on Alpha Date: Tue, 04 Apr 2006 04:24:16 -0400 Message-ID: <44322D30.9070804@garzik.org> References: <1br232p2g092l611qrqvmvpuus2bqp7bc2@4ax.com> <4431CF4D.6000806@gmail.com> <4431D5F5.4010905@tw.ibm.com> <4431D6D1.9020206@gmail.com> <4431DEA3.5040202@tw.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:22214 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S1751844AbWDDIYX (ORCPT ); Tue, 4 Apr 2006 04:24:23 -0400 In-Reply-To: <4431DEA3.5040202@tw.ibm.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: albertl@mail.com Cc: Tejun Heo , Jonathan Blake Benson , linux-ide@vger.kernel.org Albert Lee wrote: > Tejun Heo wrote: >> Albert Lee wrote: >> >>> Tejun Heo wrote: >>> >>>> Jonathan Blake Benson wrote: >>>> >>>>> I posted a couple of months ago regarding enabling libata.atapi on a >>>>> Digital Alpha 164LX, equipped with a Silicon Image 3114 controller. I >>>>> decied to give kernel 2.6.16 (release, was previously using rc-1) a >>>>> shot, and it no longer longer panics. I still have a Lite-ON DVD ROM >>>>> drive connected via a sil3611 bridge to port number 4, hoping that I >>>>> can avoid using the onboard CMD646. >>>>> >>>>> No panic this time, though it appears to throw a machine check. The >>>>> system continues all the way to multi-user, and the Maxtor drives are >>>>> usable. Hope the attached dmesg helps. Let me know if I can be of >>>>> any assitance. >>>>> >>>> Can you build your kernel with ATA_DEBUG set and post dmesg? Just >>>> change #undef ATA_DEBUG to #define ATA_DEBUG at the top of >>>> include/linux/libata.h >>>> >>> For the SiI 3611 bridge + ATAPI devices, maybe the ATAPI_ENABLE_DMADIR >>> workaround should also be turned on as well. (in linux/libata.h) >>> >>> My JMicron 20330 bridge + SiI 3112 can handle ATAPI DMA without >>> the ATAPI_ENABLE_DMADIR workaround. However, the SiI 3611 bridge seems >>> need it. >> >> Is there any way to make this thing automatic? 'Recompile with #define >> tweak if you have some invisible bridge chip' doesn't sound too hot. >> > > The bridge is transparent to the software. So, it's hard to detect the chip > used. Maybe the SiImage developers know how to detect the chip? There's a spec for DMADIR on t13.org, with IDENTIFY DEVICE bits to recognize, etc. Jeff