From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752820AbXDDXWE (ORCPT ); Wed, 4 Apr 2007 19:22:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752822AbXDDXWD (ORCPT ); Wed, 4 Apr 2007 19:22:03 -0400 Received: from mail.tmr.com ([64.65.253.246]:57579 "EHLO gaimboi.tmr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752817AbXDDXWA (ORCPT ); Wed, 4 Apr 2007 19:22:00 -0400 Message-ID: <46143338.3020808@tmr.com> Date: Wed, 04 Apr 2007 19:22:32 -0400 From: Bill Davidsen Organization: TMR Associates Inc, Schenectady NY User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061105 SeaMonkey/1.0.6 MIME-Version: 1.0 To: Tejun Heo CC: linux@horizon.com, dan.j.williams@intel.com, linux-ide@vger.kernel.org, neilb@suse.de, cebbert@redhat.com, jens.axboe@oracle.com, linux-kernel@dale.us, linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org Subject: Re: 2.6.20.3 AMD64 oops in CFQ code References: <20070323174630.31051.qmail@science.horizon.com> <4611EADC.3000306@suse.de> In-Reply-To: <4611EADC.3000306@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Tejun Heo wrote: > [resending. my mail service was down for more than a week and this > message didn't get delivered.] > > linux@horizon.com wrote: > >>> Anyway, what's annoying is that I can't figure out how to bring the >>> drive back on line without resetting the box. It's in a hot-swap >>> > enclosure, > >>> but power cycling the drive doesn't seem to help. I thought libata >>> > hotplug > >>> was working? (SiI3132 card, using the sil24 driver.) >>> > > Yeah, it's working but failing resets are considered highly dangerous > (in that the controller status is unknown and may cause something > dangerous like screaming interrupts) and port is muted after that. The > plan is to handle this with polling hotplug such that libata tries to > revive the port if PHY status change is detected by polling. Patches > are available but they need other things to resolved to get integrated. > I think it'll happen before the summer. > > Anyways, you can tell libata to retry the port by manually telling it to > rescan the port (echo - - - > /sys/class/scsi_host/hostX/scan). > I won't say that's voodoo, but if I ever did it I'd wipe down my keyboard with holy water afterward. ;-) Well, I did save the message in my tricks file, but it sounds like a last ditch effort after something get very wrong. -- bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979