All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Tyler Montbriand <tsm@accesscomm.ca>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: sata_sil on amd64
Date: Sun, 23 Jan 2005 17:29:50 +0100	[thread overview]
Message-ID: <58cb370e050123082935e29d4f@mail.gmail.com> (raw)
In-Reply-To: <200501221919.35710.tsm@accesscomm.ca>

On Sat, 22 Jan 2005 19:19:35 -0600, Tyler Montbriand <tsm@accesscomm.ca> wrote:
> I have been stuck using kernel 2.6.4 for the last year or so for various
> reasons, and now I'm in a vicious catch-22.  If I don't upgrade, I can't use
> NPTL, therefore my system will continue to be susceptible to the
> sigqueue-overflow flaw in linuxthreads.  But if I do upgrade, problems in
> >0.53 sata_sil implementations halt my system in a matter of minutes with
> dmesg entries about imaginary bad blocks.
> 
> 0.53 probably has it's own flaws, but it's been rock-solid running a single
> drive on my computer for a year.  How feasible would it be to forward-port
> this version to a newer kernel, say 2.6.10?  If I fix the header problems
> could it work, or is .10 too structurally different from .4?

Alternatively if you pinpoint the kernel snapshot which introduces this behavior
(-bk patches are available at kernel.org) we may be able to fix sata_sil.

Bartlomiej

      reply	other threads:[~2005-01-23 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23  1:19 sata_sil on amd64 Tyler Montbriand
2005-01-23 16:29 ` Bartlomiej Zolnierkiewicz [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=58cb370e050123082935e29d4f@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=tsm@accesscomm.ca \
    /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.