sreadahead crashed with SIGSEGV in __pause_nocancel()

Bug #434948 reported by Simon Déziel
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sreadahead (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: sreadahead

I boot my laptop and logged in. After a few seconds in my gnome session, I got apport telling me that sreadahead had crash.

I don't know if it's releated but my hard drive is reported to be in pre-fail state by gnome-disk-utility. Anyway, segfaults are never good, even when the hard drive is dying.

ProblemType: Crash
Architecture: amd64
Date: Tue Sep 22 15:42:26 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-10.34-generic
SegvAnalysis:
 Segfault happened at: 0x401ed5: mov (%r15,%rdi,1),%dil
 PC (0x00401ed5) ok
 source "(%r15,%rdi,1)" (0x7f6d501ed010) 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-10-generic x86_64
UserGroups:

Simon Déziel (sdeziel)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-amd64-retrace
Revision history for this message
Moreno Bartalucci (moreno-bartalucci) wrote :

I'm having a very similar problem on kubuntu amd64 karmic.
I tried to jump to the original bug report (#414597) but it says "I'm not allowed to see that page": is it normal?

In my case I disabled the crash reports so I don't get any but once the pc is booted up I can see in dmesg this:

Sep 24 08:12:25 nbmoreno kernel: [ 92.029820] sreadahead[442]: segfault at 7f286c6a8010 ip 0000000000401ed5 sp 00007fffdd00d0f0 error 4 in sreadahead[400000+3000]

Furthermore, the file /var/lib/sreadahead/pack is *NEVER* created.

I don't know if it's helpful, though I tried to run sreadhead as root with strace *after* the boot, so:

root@nbmoreno:~# strace sreadahead --no-fork 2> strace.txt

gave the result as attached: segmentation fault

Any help is greatly appreciated!

Revision history for this message
Simon Déziel (sdeziel) wrote :

I have the same problem accessing the bug #414597. Maybe some else can help us on that.

I haven't traced sreadahead but I can confirm that I have not the file /var/lib/sreadahead/pack.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.