PCI resource errors and unable to reboot system

[shuttleworthwannabe]

Hardware HP Compaq nw8240 Pentium Cntrino 2.13GHz 2G RAM 80 5400RPM HDD ATI Mobility FireGL V5000 15.4" UXGA widescreen
Dapper Drake 20060410 Daily build

This is my first bug report, so I have very little experience in reporting this. I will do my best to explain. I am also fairly new to Linux but am a quick learner. I have been using Ubuntu since january 2006 and dapper when it was flight 2 or 3.

Whenever I boot dapper I get this meesage at boot up screen just prior to the splash screen:
==
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.1
===

But thh system boots normally into the GUI login screen.
However, when i want to reboot the system, the system hangs and in console I see this message:
==
[4294829.614000] No reboot fixup found for your hardware
==
NOTE: with Breezy I can reboot normally without any errors as above. and with Dapper prior to 5+ I could reboot normally, something in Dapper 5+ has changed to cause this reboot problem.

I have the ATI fglrx drivers installed from Ubuntu and I know it is working, kinda, because whenver I log out as user, the login screen flickers and the omage if unclear; I have to ctrl alt and backspace to reload the X server.

Here is my fglrxinfo:
==
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY FireGL V5000 Pentium 4 (SSE2) (FireGL) (GNU_ICD)
OpenGL version string: 2.0.5695 (8.23.7)
==

I can post my xorg.conf if needed.

Thank you for taking this report.
Shu

[Ben Collins (ben-collins)]

Please attach (do no paste in comment) the entire output of dmesg.

[shuttleworthwannabe (skauchali)]

Hi Ben, Sorry how do I attach this to the comment? There is not facility to do this..like dialogue to "attach file" or attachment?

[shuttleworthwannabe (skauchali)]

I guess I will have to send this via my email then. Thanks for reviewing my
report. the dmeg is attached.

Shuaib

On 4/13/06, Ben Collins <email address hidden> wrote:
>
> Please attach (do no paste in comment) the entire output of dmesg.
>
> ** Changed in: linux-source-2.6.15 (Ubuntu)
> Status: Unconfirmed => Needs Info
> --
> PCI resource errors and unable to reboot system
> https://launchpad.net/malone/bugs/39138
>

[shuttleworthwannabe (skauchali)]

Hi Ben, Sorry how do I attach this to the comment? There is not facility to do this..like dialogue to "attach file" or attachment?

[Dennis Kaarsemaker (dennis)]

Check the left column :)

[shuttleworthwannabe (skauchali)]

the dmesg is attached. Thanks

[shuttleworthwannabe (skauchali)]

Just thought this would be informative as a comparison; I am attching the dmseg from Breezy. I am able to rebbot fine with breezy, no stalling. Breezy kernel is 2.6.12-10-386

Thnks for handling this,
S

[bakytn (bakytn)]

I confirm this. I'm also getting this message while booting. However the system works just fine...

[shuttleworthwannabe (skauchali)]

Note; I am testing Hardy beta release, and none of the above are noticeable; the reboot hanging is gone. In dapper to gutsy I had to add "reboot=b" to the grub menu kernel parameters to make it to reboot without hanging.

Well, something very right is happening in the Hardy development kernel; well done to the devs!

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.