mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	Pekka Enberg <penberg@kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>, Tejun Heo <tj@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] block driver updates for 2.6.38
Date: Thu, 13 Jan 2011 16:02:12 -0800	[thread overview]
Message-ID: <AANLkTikdULkbB83Us_zXivv8Y5FGdHrixUXRiitacaSh@mail.gmail.com> (raw)
In-Reply-To: <20110113141957.1eaf4940@nehalam>

On Thu, Jan 13, 2011 at 2:19 PM, Stephen Hemminger
<shemminger@vyatta.com> wrote:
>
> It looks my floppy format problem wasn't my patch but the HPET-MSI
> problem. https://patchwork.kernel.org/patch/69588/
>
> Why hasn't that been fixed in mainline kernel?

Because the proper fix was _supposed_ to be the one that disabled MSI
for just the affected AMD boards. See

  commit 73472a46b5b28116b145fb5fc05242c1aa8e1461
  Author: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
  Date:   Thu Jan 21 11:09:52 2010 -0800

    x86: Disable HPET MSI on ATI SB700/SB800

    HPET MSI on platforms with ATI SB700/SB800 as they seem to have some
    side-effects on floppy DMA. Do not use HPET MSI on such platforms.

    Original problem report from Mark Hounschell
    http://lkml.indiana.edu/hypermail/linux/kernel/0912.2/01118.html

    [ This patch needs to go to stable as well. But, there are some
      conflicts that prevents the patch from going as is. I can
      rebase/resubmit to stable once the patch goes upstream.
      hpa: still Cc:'ing stable@ as an FYI. ]

    Tested-by: Mark Hounschell <markh@compro.net>
    Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
    Cc: <stable@kernel.org>
    LKML-Reference: <20100121190952.GA32523@linux-os.sc.intel.com>
    Signed-off-by: H. Peter Anvin <hpa@zytor.com>

and if you have the same problem (MSI + floppy doesn't work), can you
give more information about your system?

In particular, is it an AMD southbridge that we don't have listed?
Right now we only trigger it for machines that match this:

  PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_SBX00_SMBUS

(which is PCI device 1002:4385) and it may be that we have incomplete coverage.

And so few people use floppies (and expect them to work), that we
probably have very bad test coverage too.

                   Linus

  reply	other threads:[~2011-01-14  0:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 13:53 Jens Axboe
2011-01-13 19:00 ` Linus Torvalds
2011-01-13 19:25   ` Jens Axboe
2011-01-13 19:40     ` Linus Torvalds
2011-01-13 21:43       ` Stephen Hemminger
2011-01-13 22:19       ` Stephen Hemminger
2011-01-14  0:02         ` Linus Torvalds [this message]
2011-01-14  0:11           ` Stephen Hemminger
2011-01-14  1:03             ` Linus Torvalds
2011-01-14  2:31               ` Stephen Hemminger
2011-01-14  4:53               ` Stephen Hemminger
2011-01-14  6:42               ` Stephen Hemminger
2011-01-14 15:55                 ` Martin Knoblauch
2011-01-20  2:01               ` Stephen Hemminger

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=AANLkTikdULkbB83Us_zXivv8Y5FGdHrixUXRiitacaSh@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=penberg@kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=tj@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

all inboxes | Powered by JetHome®