sreadahead crashed with SIGSEGV in __pause_nocancel()

Bug #422304 reported by Mark A. Hershberger
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sreadahead (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: sreadahead

looks like #421480 but reporting again to hopefully get a useful stacktrace.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Aug 31 20:12:44 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/sreadahead
Package: sreadahead 1.0-2
ProcCmdline: /sbin/sreadahead -t 0
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
SegvAnalysis:
 Segfault happened at: 0x401ed5 <mmap@plt+2661>: mov (%r15,%rdi,1),%dil
 PC (0x00401ed5) ok
 source "(%r15,%rdi,1)" (0x100007f2700f99010) 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-8-generic x86_64
UserGroups:

Revision history for this message
Mark A. Hershberger (hexmode) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__pause_nocancel () from /lib/libpthread.so.0
?? ()
__libc_start_main (main=<value optimized out>,
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Mark A. Hershberger (hexmode) wrote :

gotten this crash more than once... installing dbg packages to hopefully help

Revision history for this message
Mark A. Hershberger (hexmode) wrote :

This morning I walked into my laptop after leaving it on all night. The machine was un-responsive and the screen was blanked/powered off.

I ssh-ed into the box and tried various things (restarting gdm, killing processes, etc) but nothing seemed to work until I killed off the screensaver that was running: lorenz. At that point, the LCD panel on my laptop displayed a (non-responsive) terminal screen, but the widescreen LCD I have attached was still blank.

Nothing else I could do seemed to bring it back, so, from my ssh session, I rebooted the machine. When it came back up, this error was waiting.

I did an update yesterday.

Matt Zimmerman (mdz)
visibility: private → public
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.