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, alan@lxorguk.ukuu.org.uk, jgarzik@pobox.com
Subject: Re: PATA Sil680 Warm Plug Caused 2.6.18-rc2 Kernel Internel Error
Date: Thu, 24 Aug 2006 04:24:18 +0900	[thread overview]
Message-ID: <44ECAB62.8030804@gmail.com> (raw)
In-Reply-To: <8202f4270608231212g29e945adg23c32ad1ae132885@mail.gmail.com>

Fajun Chen wrote:
> On 8/23/06, Tejun Heo <htejun@gmail.com> wrote:
>> Fajun Chen wrote:
>> > Hi Folks,
>> >
>> > I used Linux 2.6.18-rc2 with Jeff Garzik's git libata patch for new EH,
>> > hotplug,
>> > and pata support. Hardware is ARM IOP80321 with PCI-X. Host adapters
>> > is pata Sil680.  The sequence of actions are "power off drive ->
>> > remove drive -> power on drive -> add drive" and there's kernel errors
>> > while adding the drive.  Complete dmesg traces attached. Has anyone
>> > seen this problem before?
>>
>> Can you please try the latest -mm?
> We have had issues with -mm to get it to run on our ARM IOP80321
> board.  Do you have any patches which can be applied to 2.6.18 rc2?

ISTR there has been some SCSI ref counting bug fixed recently.  I can't 
really pinpoint it.  I've taken a long look at libata-scsi after reading 
your bug report but couldn't find anything wrong although I found out 
that things can be simplified quite a bit.  I'll submit patch for that 
after resolving this issue.

Does 2.6.18-rc4 work on your platform albeit without sil680 support?  If 
so, I can send you a patch for sil680 over 2.6.18-rc4.

-- 
tejun

  reply	other threads:[~2006-08-23 19:25 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 [this message]
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
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=44ECAB62.8030804@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=fajunchen@gmail.com \
    --cc=jgarzik@pobox.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).