public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.10-ac1
Date: Mon, 27 Dec 2004 02:40:45 +0100	[thread overview]
Message-ID: <58cb370e041226174019e75e23@mail.gmail.com> (raw)
In-Reply-To: <41CF649E.20409@domdv.de>

On Mon, 27 Dec 2004 02:25:50 +0100, Andreas Steinmetz <ast@domdv.de> wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > What do you need 'serialize' option for?
> 
> I didn't check if the problem is gone with 2.6.10 but there's boards
> like my tyan 2885 which do need the serialize option to work properly
> for add-on ide controllers.
> 
>  From the X86-64 patch release notes of Andi Kleen:
> 
> Reports that dual Tyan S2885 and S2880 can lock up when multiple IDE
> channels are stressed in parallel. "noapic" or "ideX=serialize" seems to
> work around it. Andre Hedrick thinks it's a generic bug/race in the IDE
> code.
>
> Do you want to force people to disable the io-apic just because of
> option removal? In my case the serialized devices are a disk and a
> dvd-rw which is rarely used, so disabling the io-apic is a bad solution.

No, I want them to fix the problem - whenever it is - ide or apic code. :)

  reply	other threads:[~2004-12-27  1:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-26 23:31 Linux 2.6.10-ac1 Alan Cox
2004-12-27  0:57 ` Bartlomiej Zolnierkiewicz
2004-12-27  1:25   ` Andreas Steinmetz
2004-12-27  1:40     ` Bartlomiej Zolnierkiewicz [this message]
2004-12-27 14:28       ` Alan Cox
2004-12-27 15:46         ` Bartlomiej Zolnierkiewicz
2004-12-27 14:45       ` Ross Biro
2004-12-27 15:38         ` Bartlomiej Zolnierkiewicz
2004-12-27 15:49           ` Andreas Steinmetz
2004-12-27 15:54             ` Bartlomiej Zolnierkiewicz
2004-12-27 16:02               ` Andreas Steinmetz
2004-12-27 16:54               ` Alan Cox
2004-12-27 14:36     ` Rafael J. Wysocki
2004-12-27 14:57       ` Andreas Steinmetz
2004-12-27 14:33   ` Alan Cox
2004-12-27 20:31     ` Rogério Brito
2004-12-27 20:43       ` Michal Schmidt
2004-12-28  0:45         ` Alan Cox
2004-12-28  2:44           ` Rogério Brito
2004-12-30  4:41 ` Gene Heskett
2004-12-30  5:05 ` Gene Heskett
2004-12-30 23:38   ` Alan Cox
2004-12-31  1:06     ` Gene Heskett
2004-12-31  9:57       ` Jan Dittmer
2004-12-31 12:05         ` Gene Heskett
2004-12-31 12:38           ` Jan Dittmer
2004-12-31 13:18             ` Gene Heskett

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=58cb370e041226174019e75e23@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ast@domdv.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox