ubuntu 8.10 beta boot failure - patch attached

Its a real bug, but only your computer have it, cause in mine this doesn`t happened. I hope you could get a right answer.

No one can help? Is there not any advice or hint to solve this problem? No one have the same experience like me?

I am the same mistakes!
However, my configuration is:
i have an ASUS P5QL-PRO motherboard with a onboard ethernet card Atheros AR8121/AR8113/AR8114,
a NVIDIA GeForce 9600 GT video card, a SATA 250G harddisk, an Intel E7200 cpu.
The reason is estimated that motherboard!

Seems to be the motherboard, I too have an ASUS P5QL-PRO.

I have the same problem with P5QL-Pro and Intrepid alpha6.

This is not an Ubuntu specific bug.

I did some more testing with other distributions and they both trigger the same bug (with slightly different error messages):
- Fedora 10 beta x86_64 (Kernel 2.6.27)
- openSUSE 11.0 i386 (Kernel 2.6.25)

So I guess this bug has been introduced in 2.6.25.
Is there a way to obtain more debugging information?

I have tried some older versions (6.10 and 7.04). I do not know what kernel these are based on, but they do not work either. Secondly, I'm just trying to pull some attention to this bug because I hate this one :)

Tested with intrepid beta:

PANIC: early exception 0e rip 10:ffffffff812aeaed error 0 cr2 ffffffffff341000

I booted Intrepid with the parameter earlyprintk=vga
Here are the photos of the kernel output.

Same problem with Intrepid beta and Asus P5QL PRO motherboard

I tracked the bug down to this commit (between 2.6.24 and 2.6.25-rc1):
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1fd6a53ddc75d02ad0f363cb42f2a1cec6b701c2

Same problem with Asrock K7S8XE+ :(

Oh, my system boots with linux-image-2.6.25-2-386, but linux-image-2.6.27-4-generic leads to the error: BUG Int 14 : CR2

There is an upstream patch available, that didn't make it into 2.6.27 final:
http://lkml.org/lkml/2008/10/9/267 (attached for convenience)

Please add it to the intrepid kernel.
I can confirm that it fixes this bug.

@Felix:

Can you ask Alan if he could send it to the stable kernel serie ?
Since it seems trivial and it fixes a regression, it looks to be the best thing to do (and that way it will automatically propagate to all the distros that use 2.6.27)

thanks.

Any chance to get this on the Ubuntu version of the kernel shipped with 8.10 till we wait for 2.6.27.1 ?
It is pretty scary the prospect of updated Hardy's systems unable to boot anymore

BTW, the patch is already included in 2.6.27-git3 (as of this writing the last stable kernel)

Same problem with Gigabyte GA-EP45-DS3P

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=commit;h=2f5702114e8d98e4585fd194151cdba1d3365067

This bug was fixed in the package linux - 2.6.27-7.11

---------------
linux (2.6.27-7.11) intrepid; urgency=low

  [ Amit Kucheria ]

  * STABLE queue: mac80211: fix two issues in debugfs
    - LP: #275227
  * SAUCE: Adds support for COMPAL JHL90 webcam

  [ Ben Collins ]

  * SAUCE: (no-up) x86: Quiet "Kernel alive" messages
    - LP: #39985
  * SAUCE: (no-up) Modularize vesafb
  * build/config: Enable vesafb module
  * build: Switch to vesafb as preferred.

  [ Leann Ogasawara ]

  * Add Dell Dimension 9200 reboot quirk
    - LP: #271370

  [ Michael Haas ]

  * SAUCE: Revert aufs changes from AppArmor merge

  [ Tim Gardner ]

  * fix virtio udeb layout
    - LP: #257739
  * Enabled CONFIG_EXT4DEV_FS=m
  * Changed default TCP congestion algorithm to 'cubic'
    - LP: #278801
  * SAUCE: ipw2200: change default policy for auto-associate
    - LP: #264104

  [ Upstream Kernel Changes ]

  * x86, early_ioremap: fix fencepost error
    - LP: #263543

 -- Tim Gardner <email address hidden> Sat, 11 Oct 2008 08:07:42 -0600

I have the problem with th latest kernel version from stable release 8.10. my board is Gigabyte GA-M61P-S3

when i reset the computer it works. if i start the computer after i've unplugged the powercable the error will displayed.

Marco, why do you think that your problem is the same as this bug?

i have search for BUG Int 14 and i found only this bug

I tried to Install Ubuntu Intrepid on my new PC that didn't have an OS preinstalled and encountered this very bug. What would be the best way of installing Intrepid on this machine? I guess there's no updated Intrepid media that contains the patched kernel. Seems like there's no other way than installing Hardy and upgrading to Intrepid, right?

This bug has been fixed before the Intrepid release.
So I think something else causes your problem.

Hi Felix,

I just noticed that I didn't use the final version of Intrepid, but an Alpha or Beta medium that was lying around. Installing Intrepid using the official ISO worked just fine. Sorry for bothering you.

"Int 14" is fairly generic as an error, and the bug reported here definitely appears to be resolved. Again marking as fixed. Marco, you may want to open a new bug report with more detail about your issue.

I downloaded ubuntu-8.10-desktop-i386.iso a couple of weeks ago and I get an identical problem. The installation process stops shortly after displaying "Booting the kernel" and shows the error message:
    BUG: Int 14 : CR2 ffb41000
and then locks up.

The system has an Asus P5QL motherboard with a Core 2 Duo E8500 and 4 GB RAM.

It's disappointing to see that, although this bug appears to have been known about for some months, there is no mention of it in the 8.10 release notes.

Are you sure you are using the final Intrepid version?

Like Steve said "BUG: Int 14" is a generic error message, so it might be a different bug.