From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: PATA Sil680 Warm Plug Caused 2.6.18-rc2 Kernel Internel Error Date: Sat, 26 Aug 2006 03:00:08 +0900 Message-ID: <44EF3AA8.6040100@gmail.com> References: <8202f4270608230906r73b1d91bj279bfc0ef4b7a39d@mail.gmail.com> <44ECAB62.8030804@gmail.com> <8202f4270608231255k116918dfk58e4c14cd859c175@mail.gmail.com> <8202f4270608231349v5aabace2xaff8fe93c133a7ca@mail.gmail.com> <20060824070257.GD21866@htj.dyndns.org> <8202f4270608240942i6b620961t1a03d4148dd4a32d@mail.gmail.com> <44EDDB91.1050102@gmail.com> <8202f4270608241701g494bfadaw74dd3d059182e4cc@mail.gmail.com> <8202f4270608250826h67edf5d7n8436961374896348@mail.gmail.com> <44EF18BC.8040505@gmail.com> <8202f4270608251027j4ae31243laab8a6bd3e433697@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from py-out-1112.google.com ([64.233.166.182]:30755 "EHLO py-out-1112.google.com") by vger.kernel.org with ESMTP id S1751462AbWHYSAO (ORCPT ); Fri, 25 Aug 2006 14:00:14 -0400 Received: by py-out-1112.google.com with SMTP id n25so1335231pyg for ; Fri, 25 Aug 2006 11:00:14 -0700 (PDT) In-Reply-To: <8202f4270608251027j4ae31243laab8a6bd3e433697@mail.gmail.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Fajun Chen Cc: "linux-ide@vger.kernel.org" Fajun Chen wrote: > Hi Tejun, > > Below are the tests I performed: > Test1: > a) Power off the drive > b) echo "scsi remove-single-device h b t l" > /proc/scsi/scsi > or delete using sysfs > c) Power on the drive > d) echo "scsi add-single-device h b t l" > /proc/scsi/scsi > or scan using sysfs > The kernel error in my first email is induced in this test but not > consistently reproducible. In most of the case, no kernel error but sg > was not reattached when adding device. > > Test2: > Ignore step c) in test1. Basically, try to add device while the device > is still powered off. > > Hope this helps. Was the drive loaded with commands issued via /dev/sgX when you did above operation? -- tejun