All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Daniel Drake <dsd@gentoo.org>, CaT <cat@zip.com.au>,
	linux-kernel@vger.kernel.org
Subject: Re: IT8212/ITE RAID
Date: Sun, 14 Aug 2005 17:56:37 +0200	[thread overview]
Message-ID: <58cb370e050814085613ccc42c@mail.gmail.com> (raw)
In-Reply-To: <1124034767.14138.55.camel@localhost.localdomain>

On 8/14/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Sul, 2005-08-14 at 17:01 +0200, Bartlomiej Zolnierkiewicz wrote:
> > > Thats probably the fact other patches from -ac are missing in base. It
> > > should be harmless.
> >
> > Therefore please submit them.
> 
> Cut the crap, you know I've submitted the stuff again and again and
> again along with other fixes, reports of stuff you broke you ignored
> etc. So I got bored of playing your games.

* your stuff was accepted after all (and some stuff like ide-cd
  fixes was never splitted from the -ac patchset and submitted)

* you've never provided any technical details on "the stuff I broke"

Can't you get over this bullshit please?  Life goes on.

> > > > > [227523.229631] hda: cache flushes not supported
> > > > > [227523.229932]  hda:hda: recal_intr: status=0x51 { DriveReady SeekComplete Error }
> > > > > [227523.230905] hda: recal_intr: error=0x04 { DriveStatusError }
> > > > > [227523.230952] ide: failed opcode was: unknown
> > >
> > > Yep - on my "wtf" list. In some cases we send a strange command to the
> > > IT8212 drive. I'm still trying to find the guilty command we send (none
> > > of my drives do this), so that I can fix the ident adjustment to stop
> > > it. The noise is just the command being rejected which is ok but messy
> > > and wants stomping.
> >
> > small hint: WIN_RESTORE
> 
> Would make sense, but I thought I had the right bits masked. Will take a

WIN_RESTORE is send unconditionally (as it always was),

This is not the right thing, somebody should go over all ATA/ATAPI
drafts and come with the correct strategy of handling WIN_RESTORE.

> look tomorrow however.

  reply	other threads:[~2005-08-14 15:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14  5:30 IT8212/ITE RAID CaT
2005-08-14 11:08 ` Daniel Drake
2005-08-14 11:47   ` CaT
2005-08-14 12:44     ` Daniel Drake
2005-08-14 13:33       ` Alan Cox
2005-08-14 15:01         ` Bartlomiej Zolnierkiewicz
2005-08-14 15:52           ` Alan Cox
2005-08-14 15:56             ` Bartlomiej Zolnierkiewicz [this message]
2005-08-14 21:13               ` Alan Cox
2005-08-14 21:20                 ` Bartlomiej Zolnierkiewicz
2005-08-22  9:28                   ` Bartlomiej Zolnierkiewicz
2005-08-22 10:33                     ` Alan Cox
2005-08-22 10:21                       ` Bartlomiej Zolnierkiewicz
2005-08-22 23:48                     ` Andre Hedrick
2005-08-14 23:59         ` CaT
2005-08-16 22:41         ` CaT
2005-08-14 21:09   ` James Tabor

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=58cb370e050814085613ccc42c@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cat@zip.com.au \
    --cc=dsd@gentoo.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.