mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Lever <cel@citi.umich.edu>
To: linux-kernel@vger.kernel.org
Subject: 2.6.17-rc3 PCI init hang
Date: Mon, 01 May 2006 15:04:25 -0400	[thread overview]
Message-ID: <44565BB9.8020504@citi.umich.edu> (raw)

I have a dual Pentium III I use for testing.  Since late last week 
(around about 2.6.17-rc3) it hangs during boot just after "Setting up 
standard PCI resources".  2.6.17-rc2 works fine.

A push in the right direction would be appreciated.  Please reply off 
list as I'm not subscribed.

...

PCI: PCI BIOS revision 2.10 entry at 0xfdbc1, last bus=1
Setting up standard PCI resources

 >>> 2.6.17-rc3 stops here and hangs.
 >>> 2.6.17-rc2 continues with:

PCI: Probing PCI hardware
PCI: Discovered peer bus 01
PCI: Using IRQ router ServerWorks [1166/0200] at 0000:00:0f.0
PCI->APIC IRQ transform: 0000:00:03.0[A] -> IRQ 31
PCI->APIC IRQ transform: 0000:01:03.0[A] -> IRQ 23
PCI: Cannot allocate resource region 0 of device 0000:00:0f.2
...

lspci -v:

00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
         Flags: bus master, medium devsel, latency 32

00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 06)
         Flags: bus master, medium devsel, latency 16

00:01.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) 
(prog-if 00 [VGA])
         Subsystem: ATI Technologies Inc Rage XL
         Flags: bus master, stepping, medium devsel, latency 64
         Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
         I/O ports at d800 [size=256]
         Memory at feaff000 (32-bit, non-prefetchable) [size=4K]
         Expansion ROM at feac0000 [disabled] [size=128K]
         Capabilities: <available only to root>

00:03.0 RAID bus controller: Promise Technology, Inc. PDC20267 
(FastTrak100/Ultra100) (rev 02)
         Subsystem: Promise Technology, Inc.: Unknown device 4d32
         Flags: bus master, medium devsel, latency 64, IRQ 31
         I/O ports at dfe0 [size=8]
         I/O ports at dfac [size=4]
         I/O ports at dfa0 [size=8]
         I/O ports at dfa8 [size=4]
         I/O ports at df00 [size=64]
         Memory at feaa0000 (32-bit, non-prefetchable) [size=128K]
         Expansion ROM at feae0000 [size=64K]
         Capabilities: <available only to root>

00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 50)
         Subsystem: Broadcom OSB4 South Bridge
         Flags: bus master, medium devsel, latency 0

00:0f.1 IDE interface: Broadcom OSB4 IDE Controller (prog-if 8a [Master 
SecP PriP])
         Flags: bus master, medium devsel, latency 64
         I/O ports at ffa0 [size=16]

00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 04) 
(prog-if 10 [OHCI])
         Subsystem: Broadcom OSB4/CSB5 OHCI USB Controller
         Flags: medium devsel
         Memory at 30000000 (32-bit, non-prefetchable) [size=4K]

01:03.0 Ethernet controller: Netgear GA630 Gigabit Ethernet (rev 01)
         Subsystem: Netgear GA630 Gigabit Ethernet
         Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 23
         Memory at febfc000 (32-bit, non-prefetchable) [size=16K]

-- 
corporate:	<cel at netapp dot com>
personal:	<chucklever at bigfoot dot com>

             reply	other threads:[~2006-05-01 19:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01 19:04 Chuck Lever [this message]
2006-05-03 12:41 ` Andrew Morton
2006-05-03 15:32   ` Chuck Lever
2006-05-04 21:30 ` Andrey Melnikoff

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=44565BB9.8020504@citi.umich.edu \
    --to=cel@citi.umich.edu \
    --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

Powered by JetHome