pci-express non-fatal error crash my system on boot, 8.10

[dano]

pci-express non-fatal error crash my system on boot in intrepid ibex 8.10
the pc speaker starts to sound as if it were a memory error and the screens and the screen turned black

I have no other information because I had to return to the previous version 8.04 (this works great)

[Steve Beattie (sbeattie)]

Thank you for helping to make Ubuntu better. This looks like a kernel issue; however, more information is needed to identify the exact problem you are seeing. Please attach the output from running the following commands:

  - uname -a > uname-a.log
  - cat /proc/version_signature > version.log
  - dmesg > dmesg.log
  - sudo lspci -vvnn > lspci-vvnn.log

The information at https://wiki.ubuntu.com/KernelTeamBugPolicies#Problems%20in%20capturing%20information may be helpful in capturing this information.

[Joakim Lundborg (joakim-lundborg)]

I have the same problem. Here are the logs I was able to catch (lspci won't run when the system is started)
The results are not exactly the same every time I boot, sometimes I won't even get to a root prompt.

Booting in 2.6.24 works fine with no errors. Also note that I get no ext3 errors in 2.6.24, so this is somehow related.

[Joakim Lundborg (joakim-lundborg)]

This is the kernel version:
Ubuntu 2.6.27-5.8-generic
Linux cimex 2.6.27-5-generic #1 SMP Fri Oct 3 00:36:38 UTC 2008 x86_64 GNU/Linux

[Steve Beattie (sbeattie)]

This bug was reported in the Intrepid development cycle; removing regression-potential and marking as regression-release.

[Leann Ogasawara (leannogasawara)]

Hi guys,

Just curious if anyone who had this issue was able to test the latest Jaunty 9.04 release yet?

http://www.ubuntu.com/getubuntu/download

The reason I ask is because it contains a newer 2.6.28 based kernel. Additionally a bug must be confirmed as fixed in the latest development release before it could be considered for a Stable Release Update - https://wiki.ubuntu.com/StableReleaseUpdates . Please let us know your results if you are able to test. Thanks.

[Leann Ogasawara (leannogasawara)]

Having had no feedback for 7 weeks I'm closing this bug for now. Please feel free to reopen if you are able to confirm this issue remains in the latest release. To reopen the bug just set the Status back to New. Thanks.