system freezes when I turn on the link in firefox

[Pavel-II]

System freezes when I turn on the link in firefox.
They think it's a kernel bug http://unixforum.org/index.php?showtopic=119349
This link http://itmages.ru/image/view/72092/53824e1f

I`m run sleep 30s; firefox http://itmages.ru/image/view/72092/53824e1f and go to tty1. You can see 2 images in attachment and output `ps lax` in loop when the firefox is go to fatal link.

On the other Computers mistake is not repeated

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: upstart 0.6.6-3
ProcVersionSignature: Ubuntu 2.6.35-23.36-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Thu Nov 4 20:17:33 2010
ExecutablePath: /sbin/init
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
ProcEnviron: PATH=(custom, no user)
SourcePackage: upstart

[Nicola Ferralis (feranick)]

Thanks for reporting this bug. On maverick (i386) I cannot replicate this bug. I can open the link with no issues.

[Pavel-II (dzy4)]

I`m boot from liveCD.
On tty1:
http://itmages.ru/image/view/74661/70892f98
first line: "BUG: unable to handle kernel NULL pointer dereferences at 00000014"

[Fabio Marconi (fabiomarconi)]

Not reproducible in gnome-terminal and tty

[Pavel-II (dzy4)]

On tt1 in w3m all is well, without bug.

[Victor Vargas (kamus)]

Have you tried to reproduce this issue using latest ISO release of Ubuntu Maverick? by the way, I am not able to reproduce it here too.

[Pavel-II (dzy4)]

Re:Have you tried to reproduce this issue using latest ISO release of Ubuntu Maverick? by the way, I am not able to reproduce it here too.
No, it`s by Sun Sep 19 20:34:50 UTC 2010.
Now downloading last release.
But if the latest release of the error will not happen again, what can I do with my installed version? Last update.

[Pavel-II (dzy4)]

I`m download this http://releases.ubuntu.com/maverick/ubuntu-10.10-alternate-amd64.iso.torrent
and it`s without live mode

[Pavel-II (dzy4)]

i`m install http://releases.ubuntu.com/maverick/ubuntu-10.10-alternate-amd64.iso
$ uname -a
Linux ubuntu 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010 x86_64 GNU/Linux
Bug repeated.

[Pavel-II (dzy4)]

How can I determine what went wrong?

[Pavel-II (dzy4)]

I`m add to /etc/apt/sources.list

deb http://ppa.launchpad.net/ubuntu-mozilla-daily/ppa/ubuntu maverick main
deb http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu maverick main

then run sudo apt-get update

and go to fatall link.

The same.

http://static.itmages.ru/i/10/1115/h_1289845827_00f43cd857.png

[Pavel-II (dzy4)]

They are fix it

http://lkml.org/lkml/2010/11/8/218
http://lkml.org/lkml/2010/11/9/147

As soon as these will be included in Ubuntu?

[Jeremy Foshee (jeremyfoshee)]

Hi rich,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Pavel-II (dzy4)]

uname -r 2.6.37-999-generic

it`s ok. Whith out bug! : )

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]