From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: Matthew Wilcox <willy@debian.org>
Cc: Randolph Chung <tausq@debian.org>,
patrick@tykepenguin.com, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] kdb getting healthier? (PCI guru needed, that's you willy!)
Date: Thu, 6 Jun 2002 10:43:45 -0400 [thread overview]
Message-ID: <20020606104345.D7198@systemhalted> (raw)
In-Reply-To: <20020606150944.D27186@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Thu, Jun 06, 2002 at 03:09:44PM +0100
>
> that ugly macro expands into inb/inw/inl. that printk probably needs to
> go away -- i don't think it's helpful. maybe it should stay for adapter
> != 0, but so many drivers probe ISA space for their devices that we're
> going to keep getting them.
>
> i bet the loop isn't infinite... probably driver probing. If you turn
> off CONFIG_PCI, the driver shouldn't be compiled in.
>
Ah, excellent. I think I understand how that works.
Sadly, I'm not so sure that's the case, since it prints:
---
PCI or EISA Bus Adapter 0 is not registered. in8(0x64) returning -1;
" in8(0x60) returning -1;
---
This message is not an exact copy since my notes are at home.
This printk alternates, dare I say, forever? (I'll leave it running for
a few hours and see what happens).
I'll try and figure out what, if any, driver is broken.
Most importantly I'll disable PCI/EISA support for now and see how
far the system boots.
Thanks W!
c.
next prev parent reply other threads:[~2002-06-06 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 13:21 [parisc-linux] kdb getting healthier? (PCI guru needed, that's you willy!) Carlos O'Donell Jr.
2002-06-06 14:09 ` Matthew Wilcox
2002-06-06 14:43 ` Carlos O'Donell Jr. [this message]
2002-06-06 16:19 ` John David Anglin
2002-06-06 18:57 ` Carlos O'Donell Jr.
2002-06-06 19:35 ` John David Anglin
2002-06-07 15:08 ` Carlos O'Donell Jr.
2002-06-07 16:42 ` John David Anglin
2002-06-07 16:48 ` Matthew Wilcox
2002-06-07 17:01 ` John David Anglin
2002-06-07 17:06 ` Matthew Wilcox
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=20020606104345.D7198@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=patrick@tykepenguin.com \
--cc=tausq@debian.org \
--cc=willy@debian.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