The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Benjamin Weber <shawk@gmx.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	Andrew Morton <akpm@digeo.com>,
	Andrew de Quincey <adq_dvb@lidskialf.net>
Subject: [BUG mm-tree of test2/test3] nforce2-acpi-fixes breaks via ide controller
Date: 10 Aug 2003 18:40:32 +0200	[thread overview]
Message-ID: <1060533632.3886.19.camel@athxp.bwlinux.de> (raw)

Hi all

Since the test2-mm1 sources I get the following error during boot:

VP_IDE: IDE controller at PCI slot 0000:00:11.1
VP_IDE: (ide_setup_pci_device:) Could not enable device.

This results in not being able to use DMA for any devices connected to
my IDE controller. Hdparm says permission denied when I do a hdparm -d1
/dev/hda e.g.

I checked with a vanilla kernel and everything is working fine there.
Going through the broken-out patches from Andrew Morton I found the one
patch that caused the above behavior: nforce2-acpi-fixes.patch

I do not know why it should interfere with my via stuff, but it does. A
vanilla test3 kernel is working fine as well, whereas test3-mm1 shows
the same error as before with test2-mmX.

My board is a ECS K7VTA3 Rev. 5.0. Vanilla Kernel reports the chipset
as:
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1

Hope the above information is enough. I can provide more if needed.

--
Benjamin


             reply	other threads:[~2003-08-10 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10 16:40 Benjamin Weber [this message]
2003-08-10 21:32 ` [BUG mm-tree of test2/test3] nforce2-acpi-fixes breaks via ide controller Andrew Morton
2003-08-11  9:17   ` Andrew de Quincey
2003-08-11 11:28     ` Bartlomiej Zolnierkiewicz
2003-08-11 11:45       ` Andrew de Quincey

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=1060533632.3886.19.camel@athxp.bwlinux.de \
    --to=shawk@gmx.net \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=adq_dvb@lidskialf.net \
    --cc=akpm@digeo.com \
    --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