squid crashed with SIGABRT in __kernel_vsyscall()

This bug occurred ever since I have updated from Ubuntu version 10.10 to Ubuntu 11.04 27 day ago. The system apparently crashes consistently when you turn on the computer or reboot the system. Also, another major problems occurred since conversion to Ubuntu 11.04 the video and the screen freezes or locked out consistently without any error messages. I would appreciate if this problem fix as soon as possible. Thank you.

Hi Alex, thanks for the bug report, and sorry that it has taken a few days to get to this. Please do not report the same issue twice. I've marked the other one as a duplicate of this.

Unfortunately it seems that squid doesn't have dbg or dbgsym packages available, so its very hard to debug this crash. You would need to rebuild the source package with "DEB_BUILD_OPTIONS=nostrip debuild" and install it, then wait for the crash again.

If you need any help doing that, I'm happy to provide assistance. The steps would be:

apt-get source squid gdebi-core
gdebi squid_2.7.STABLE9-2.1ubuntu6.dsc # this installs the build-dependencies
cd squid-2.7.STABLE9
DEB_BUILD_OPTIONS=nostrip debuild binary

Then install the resulting debs.

Hi Clint Bruyn, thank you so much for responding to my posting. Apparently, I have tried the solutions you have provided, however, the solutions does not fix the problem by itself. Also, I have tried completely un-install or remove the package and re-install it again. The problem still persist. Perhaps, could this problem originated from the conversion from 10.10 to 11.04 or perhaps purging the entire system of 10.10 version and reinstall 11.04 from the scratch without system conversion. What do you think? Thanks again for your help.

Excerpts from Alex's message of Sat Jun 04 23:18:26 UTC 2011:
> Hi Clint Bruyn, thank you so much for responding to my posting.
> Apparently, I have tried the solutions you have provided, however, the
> solutions does not fix the problem by itself. Also, I have tried
> completely un-install or remove the package and re-install it again. The
> problem still persist. Perhaps, could this problem originated from the
> conversion from 10.10 to 11.04 or perhaps purging the entire system of
> 10.10 version and reinstall 11.04 from the scratch without system
> conversion. What do you think? Thanks again for your help.

Alex, what I proposed was not a solution, but rather a way to help get a
better CoreDump file with symbols included so that we can determine the
problem.

If you can still do that with the package built with 'nostrip', that would
be very helpful for determining why this error is happening. Once it crashes
with the 'nostrip' version installed, you can either report a new bug, which
will give us the new CoreDump file (btw you may want to leave it private so
that sensitive details like encryption keys and passwords aren't exposed), or
you can find the 'core' file yourself and attach it to this bug.

StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 ?? ()
 ?? ()

Status changed to 'Confirmed' because the bug affects multiple users.

This version has expired long time ago, and is no more supported