linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <teheo@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Bill Davidsen <davidsen@tmr.com>,
	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
Date: Thu, 05 Apr 2007 13:29:06 +0900	[thread overview]
Message-ID: <46147B12.60109@suse.de> (raw)
In-Reply-To: <75b66ecd0704042113mebd1275w2fa40bf159416811@mail.gmail.com>

Lee Revell wrote:
> On 4/4/07, Bill Davidsen <davidsen@tmr.com> wrote:
>> 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.

Which actually is true.  ATA ports failing to reset indicate something
is very wrong.  Either the attached device or the controller is broken
and libata shuts down the port to protect the rest of the system from
it.  The manual scan requests tell libata to give it one more shot and
polling hotplug can do that automatically.  Anyways, this shouldn't
happen unless you have a broken piece of hardware.

> Would it reallty be an impediment to development if the kernel
> maintainers simply refuse to merge patches that add new sysfs entries
> without corresponding documentation?

SCSI host scan nodes have been there for a long time.  I think it's
documented somewhere.

-- 
tejun

      reply	other threads:[~2007-04-05  4:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070322184155.GY19922@kernel.dk>
2007-03-22 18:54 ` 2.6.20.3 AMD64 oops in CFQ code linux
2007-03-22 19:00   ` Jens Axboe
2007-03-22 23:59     ` Neil Brown
2007-03-23  0:31       ` Dan Williams
2007-03-23  0:33         ` Dan Williams
2007-03-23  0:44         ` Neil Brown
2007-03-23 17:46           ` linux
2007-04-03  5:49             ` Tejun Heo
2007-04-03 13:03               ` linux
2007-04-03 13:11                 ` Tejun Heo
2007-04-04 23:22               ` Bill Davidsen
2007-04-05  4:13                 ` Lee Revell
2007-04-05  4:29                   ` Tejun Heo [this message]

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=46147B12.60109@suse.de \
    --to=teheo@suse.de \
    --cc=cebbert@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=davidsen@tmr.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@dale.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=neilb@suse.de \
    --cc=rlrevell@joe-job.com \
    /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).