From: Kianusch Sayah Karadji <kianusch@sk-tech.net>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org
Subject: PCI-Scan Hangup ...
Date: Thu, 19 Feb 2004 14:35:59 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0402191426360.27436@kryx.sk-tech.net> (raw)
Hi!
There I have a Soekris bord with some weird PCI Handup while booting
Linux during PCI-Scan .
# lspci
00:00.0 Host bridge: Cyrix Corporation PCI Master
00:12.0 ISA bridge: National Semiconductor Corporation: Unknown device 0510
00:12.1 Bridge: National Semiconductor Corporation: Unknown device 0511
00:12.2 IDE interface: National Semiconductor Corporation SCx200 IDE (rev 01)
00:12.5 Bridge: National Semiconductor Corporation: Unknown device 0515
00:13.0 USB Controller: Compaq Computer Corporation ZFMicro Chipset USB (rev 08)
There was a patch on 2.4.x which worked fine.
Now I tried to patch Kernel 2.6.x - well I'm no programmer
- I had no idea where to put it ... so I started putting some debug
messages into some files ... and suddenly including a printk(".") into
drivers/pci/probe.c fixed the whole PCI-Hangup ??? - That was not what the
2.4.x Patch did.
Hmmm ...
I've no idea why that printk fixes the Problem nor if it's a good idea to
have that printk there ...
Regards
Kianusch
--- linux-2.6.3/drivers/pci/probe.c Wed Feb 18 04:58:46 2004
+++ linux-2.6.3_geode/drivers/pci/probe.c Thu Feb 19 14:00:52 2004
@@ -656,8 +656,11 @@
DBG("Scanning bus %02x\n", bus->number);
/* Go find them, Rover! */
- for (devfn = 0; devfn < 0x100; devfn += 8)
+ for (devfn = 0; devfn < 0x100; devfn += 8) {
pci_scan_slot(bus, devfn);
+ printk(".");
+ }
+ printk("\n");
/*
* After performing arch-dependent fixup of the bus, look behind
next reply other threads:[~2004-02-19 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 13:35 Kianusch Sayah Karadji [this message]
2004-02-19 16:44 ` Bartlomiej Zolnierkiewicz
2004-02-20 0:20 ` Greg KH
2004-02-20 8:32 ` Kianusch Sayah Karadji
2004-02-20 16:58 ` Kianusch Sayah Karadji
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=Pine.LNX.4.58.0402191426360.27436@kryx.sk-tech.net \
--to=kianusch@sk-tech.net \
--cc=greg@kroah.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
all inboxes | Powered by JetHome®