Bug 9796

Summary:	Cannot allocate resource region 7 of bridge 0000:00:05.0
Product:	Drivers	Reporter:	Artem Goncharov (artem.goncharov)
Component:	PCI	Assignee:	Jesse Barnes (jbarnes)
Status:	REJECTED INSUFFICIENT_DATA
Severity:	normal	CC:	bunk, protasnb
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	2.6.24-rc8	Subsystem:
Regression:	Yes	Bisected commit-id:
Bug Depends on:
Bug Blocks:	9243

Description Artem Goncharov 2008-01-22 10:28:02 UTC

Latest working kernel version:
2.6.23.9(Fedora)
Earliest failing kernel version:
2.6.24-rc8
Distribution:
Hardware Environment: Acer Aspire 5052 (5050)
Software Environment: Fedora 8
Problem Description:
/var/log/messages:
Jan 22 20:01:10 blending kernel: PCI: Cannot allocate resource region 7 of bridge 0000:00:05.0
Jan 22 20:01:10 blending kernel: PCI: Cannot allocate resource region 8 of bridge 0000:00:05.0
Jan 22 20:01:10 blending kernel: PCI: Cannot allocate resource region 7 of bridge 0000:00:06.0
Jan 22 20:01:10 blending kernel: PCI: Cannot allocate resource region 8 of bridge 0000:00:06.0
Jan 22 20:01:10 blending kernel: PCI: Cannot allocate resource region 7 of bridge 0000:00:07.0
Jan 22 20:01:10 blending kernel: PCI: Cannot allocate resource region 8 of bridge 0000:00:07.0
...
Jan 22 20:01:10 blending kernel: system 00:01: iomem range 0xe0000000-0xefffffff could not be reserved
Jan 22 20:01:10 blending kernel: system 00:01: iomem range 0xfec00000-0xfec00fff could not be reserved
Jan 22 20:01:10 blending kernel: system 00:01: iomem range 0xfee00000-0xfee00fff could not be reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0x1080-0x1080 has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0x220-0x22f has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0x40b-0x40b has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0x4d0-0x4d1 has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0x4d6-0x4d6 has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0x530-0x537 has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0xc00-0xc01 has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0xc14-0xc14 has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0xc50-0xc52 has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0xc6c-0xc6c has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0xc6f-0xc6f has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0xcd4-0xcd5 has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0xcd6-0xcd7 has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0xcd8-0xcdf has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0x8000-0x805f has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0xf40-0xf47 has been reserved
Jan 22 20:01:10 blending kernel: system 00:08: ioport range 0x87f-0x87f has been reserved
Jan 22 20:01:10 blending kernel: system 00:09: iomem range 0xe0000-0xfffff could not be reserved
Jan 22 20:01:10 blending kernel: system 00:09: iomem range 0xfff00000-0xffffffff could not be reserved
Jan 22 20:01:10 blending kernel: system 00:09: iomem range 0x0-0xfff could not be reserved


Steps to reproduce:

Comment 1 Natalie Protasevich 2008-03-04 01:29:12 UTC

Artem, it would help if you could attach boot traces from both failing and earlier "good" kernel.
And is there a chance you could perform git bisect?

Comment 2 Jesse Barnes 2008-05-01 17:47:14 UTC

Also, can you attach the output of lspci -vvv to the bug?

Thanks,
Jesse

Comment 3 Alan 2008-09-22 10:54:16 UTC

No response in months, closing