sreadahead crashed with SIGSEGV in __pause_nocancel()

[Simon Déziel]

Binary package hint: sreadahead

I have reported the same bug (bug #434948) but it was marked as a duplicate of bug #414597. There is another person that was affected by the bug I reported and both of us are unable to access bug #414597. We get a permission denied.

For my bug with sreadahead, I've found that it only *occurs* when I open the palimpsest disk utility.

lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

apt-cache policy gnome-disk-utility
gnome-disk-utility:
  Installed: 2.28.0-0ubuntu2
  Candidate: 2.28.0-0ubuntu2
  Version table:
 *** 2.28.0-0ubuntu2 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 27 09:48:18 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/sreadahead
Package: sreadahead 1.0-3
ProcCmdline: /sbin/sreadahead -t 0
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x401ed5: mov (%r15,%rdi,1),%dil
 PC (0x00401ed5) ok
 source "(%r15,%rdi,1)" (0x7fad45eaa010) not located in a known VMA region (needed readable region)!
 destination "%dil" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: sreadahead
StacktraceTop:
 __pause_nocancel () from /lib/libpthread.so.0
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
 ?? ()
Title: sreadahead crashed with SIGSEGV in __pause_nocancel()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #414597, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.