linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Fajun Chen <fajunchen@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: PATA Sil680 Warm Plug Caused 2.6.18-rc2 Kernel Internel Error
Date: Sat, 26 Aug 2006 05:32:04 +0900	[thread overview]
Message-ID: <44EF5E44.1010002@gmail.com> (raw)
In-Reply-To: <8202f4270608251319g275ca996qb413ad41b920c044@mail.gmail.com>

Fajun Chen wrote:
> On 8/25/06, Tejun Heo <htejun@gmail.com> wrote:
>> 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?
> 
> No.   One note: the kernel error I reported in my first email
> happened in ARM XSCale IOP80321 platform.

I could regenerate an oops while the drive was loaded w/ command from 
sg.  Mine occurs earlier than yours because kmalloc debug is turned on 
(the memory is poisoned on free and the the next access oopses).  It 
seems that sg has refcounting bug.

You can issue all raw commands via high level device node - e.g. 
/dev/sdX or /dev/srX, so you don't really need to use sg devices in many 
cases.

Other than sg related, I couldn't find any problem with hot/warm/pervert 
plugging.  Can you please try without any sg use?  If you need loaded 
test, just load them with regular IO or use /dev/sdX to issue raw 
commands.  I'm not sure I'll track down the sg problem.

-- 
tejun

  reply	other threads:[~2006-08-25 20:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23 16:06 PATA Sil680 Warm Plug Caused 2.6.18-rc2 Kernel Internel Error Fajun Chen
2006-08-23 16:24 ` Tejun Heo
2006-08-23 19:12   ` Fajun Chen
2006-08-23 19:24     ` Tejun Heo
2006-08-23 19:55       ` Fajun Chen
     [not found]         ` <8202f4270608231349v5aabace2xaff8fe93c133a7ca@mail.gmail.com>
     [not found]           ` <20060824070257.GD21866@htj.dyndns.org>
     [not found]             ` <8202f4270608240942i6b620961t1a03d4148dd4a32d@mail.gmail.com>
2006-08-24 17:02               ` Tejun Heo
2006-08-25  0:01                 ` Fajun Chen
2006-08-25 15:26                   ` Fajun Chen
2006-08-25 15:35                     ` Tejun Heo
2006-08-25 17:27                       ` Fajun Chen
2006-08-25 18:00                         ` Tejun Heo
2006-08-25 20:19                           ` Fajun Chen
2006-08-25 20:32                             ` Tejun Heo [this message]
2006-08-23 16:24 ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44EF5E44.1010002@gmail.com \
    --to=htejun@gmail.com \
    --cc=fajunchen@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).