From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Tero Roponen <teanropo@cc.jyu.fi>
Cc: Jon Smirl <jonsmirl@gmail.com>,
gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc2 hangs at boot
Date: Thu, 7 Jul 2005 16:31:40 +0400 [thread overview]
Message-ID: <20050707163140.A4006@jurassic.park.msu.ru> (raw)
In-Reply-To: <Pine.GSO.4.58.0507071324560.26776@tukki.cc.jyu.fi>; from teanropo@cc.jyu.fi on Thu, Jul 07, 2005 at 01:33:46PM +0300
On Thu, Jul 07, 2005 at 01:33:46PM +0300, Tero Roponen wrote:
> 00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 02)
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR+
> Latency: 64
> Region 0: Memory at <unassigned> (32-bit, prefetchable)
^^^^^^^^^^^^
I'd bet this is the cause of your problem.
The pci_assign_unassigned_resources() is not aware of potential
problems with i386 host bridges and just reassigns this region.
Which effectively turns the DMA off on your machine, I guess.
The patch here (against clean 2.6.13-rc2) should fix that.
Ivan.
--- 2.6.13-rc2/arch/i386/pci/i386.c Thu Jul 7 15:38:54 2005
+++ linux/arch/i386/pci/i386.c Thu Jul 7 15:40:26 2005
@@ -176,10 +176,6 @@ static int __init pcibios_assign_resourc
for_each_pci_dev(dev) {
int class = dev->class >> 8;
- /* Don't touch classless devices and host bridges */
- if (!class || class == PCI_CLASS_BRIDGE_HOST)
- continue;
-
for(idx=0; idx<6; idx++) {
r = &dev->resource[idx];
@@ -195,8 +191,15 @@ static int __init pcibios_assign_resourc
* the BIOS forgot to do so or because we have decided the old
* address was unusable for some reason.
*/
- if (!r->start && r->end)
- pci_assign_resource(dev, idx);
+ if (!r->start && r->end) {
+ /* Don't touch classless devices and host
+ bridges and also hide their unassigned
+ resources from the rest of PCI subsystem. */
+ if (!class || class == PCI_CLASS_BRIDGE_HOST)
+ r->flags = 0;
+ else
+ pci_assign_resource(dev, idx);
+ }
}
if (pci_probe & PCI_ASSIGN_ROMS) {
next prev parent reply other threads:[~2005-07-07 12:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 13:47 Tero Roponen
2005-07-07 1:27 ` Jon Smirl
2005-07-07 9:59 ` Ivan Kokshaysky
2005-07-07 10:33 ` Tero Roponen
2005-07-07 12:31 ` Ivan Kokshaysky [this message]
2005-07-07 12:47 ` Tero Roponen
2005-07-07 13:41 ` Ivan Kokshaysky
2005-07-07 13:53 ` Tero Roponen
2005-07-07 14:13 ` Tero Roponen
2005-07-08 6:28 ` Ivan Kokshaysky
2005-07-08 7:57 ` [SOLVED] " Tero Roponen
2005-07-08 9:19 ` Ivan Kokshaysky
2005-07-08 9:38 ` Tero Roponen
2005-07-08 9:45 ` Ivan Kokshaysky
2005-07-07 13:59 ` Jon Smirl
[not found] ` <20050728233408.550939d4.akpm@osdl.org>
2005-07-29 8:09 ` 2.6.14-rc4: dma_timer_expiry [was 2.6.13-rc2 hangs at boot] Tero Roponen
2005-07-29 8:24 ` Andrew Morton
2005-07-29 8:35 ` Tero Roponen
2005-07-29 9:39 ` Andrew Morton
2005-08-01 7:22 ` Ivan Kokshaysky
2005-08-01 7:42 ` Tero Roponen
2005-08-04 20:49 ` 2.6.13-rc2 hangs at boot Andrew Morton
2005-07-07 13:11 Mikael Pettersson
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=20050707163140.A4006@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=gregkh@suse.de \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=teanropo@cc.jyu.fi \
/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®