sreadahead crashed with SIGSEGV in __pause_nocancel()

Bug #440046 reported by Jamie Strandboge
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sreadahead (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: sreadahead

On boot with up-to-date Karmic as of a few minutes ago, sreadahead dies on boot with the following in dmesg:
Oct 1 09:56:14 severus kernel: [ 59.282811] sreadahead[651]: segfault at 7fc2ab6b6010 ip 0000000000401f3b sp 00007fff47586570 error 4 in sreadahead[400000+3000]

gdm is not started. I had to run 'sudo start gdm' to get it to start (curiously, /etc/init.d/gdm start did *not* work). I am not sure if gdm not starting and sreadahead are related. I also did not see the splash screens on this boot. The following are what were updated before a reboot:
$ find . -mtime -3 -type f | sort
./apparmor_2.3.1+1403-0ubuntu23_amd64.deb
./apparmor-docs_2.3.1+1403-0ubuntu23_all.deb
./apparmor-utils_2.3.1+1403-0ubuntu23_amd64.deb
./gdm_2.28.0-0ubuntu8_amd64.deb
./ia32-libs_2.7ubuntu15_amd64.deb
./indicator-session_0.1.5-0ubuntu2_amd64.deb
./language-pack-en_1%3a9.10+20090926.1_all.deb
./language-pack-en-base_1%3a9.10+20090926_all.deb
./language-pack-gnome-en_1%3a9.10+20090926.1_all.deb
./language-pack-gnome-en-base_1%3a9.10+20090926_all.deb
./libapache2-mod-apparmor_2.3.1+1403-0ubuntu23_amd64.deb
./libapparmor1_2.3.1+1403-0ubuntu23_amd64.deb
./libapparmor-perl_2.3.1+1403-0ubuntu23_amd64.deb
./libelfg0_0.8.12-0ubuntu1_amd64.deb
./libnautilus-extension1_1%3a2.28.0-0ubuntu3_amd64.deb
./libnm-glib2_0.8~a~git.20090923t064445.b20cef2-0ubuntu2_amd64.deb
./libnm-util1_0.8~a~git.20090923t064445.b20cef2-0ubuntu2_amd64.deb
./libusplash0_0.5.39_amd64.deb
./mplayer_2%3a1.0~rc3+svn20090426-1ubuntu7_amd64.deb
./mplayer-nogui_2%3a1.0~rc3+svn20090426-1ubuntu7_amd64.deb
./nautilus_1%3a2.28.0-0ubuntu3_amd64.deb
./nautilus-data_1%3a2.28.0-0ubuntu3_all.deb
./network-manager_0.8~a~git.20090923t064445.b20cef2-0ubuntu2_amd64.deb
./software-center_0.4.3_all.deb
./tasksel_2.73ubuntu22_all.deb
./tasksel-data_2.73ubuntu22_all.deb
./ubuntu-xsplash-artwork_0.8.1-0ubuntu2_amd64.deb
./usplash_0.5.39_amd64.deb
./xsplash_0.8.1-0ubuntu2_amd64.deb

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Oct 1 09:41:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/sreadahead
Package: sreadahead 1.0-4
ProcCmdline: /sbin/sreadahead -t 0
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x401f3b: mov (%r15,%rdi,1),%dil
 PC (0x00401f3b) ok
 source "(%r15,%rdi,1)" (0x7fb39b883010) 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:

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

The following bugs are likely duplicates, but apport has not unprivated them yet:
bug 422304
bug 427314
bug 429187
bug 430020

I'd be happy to subscribe a developer to the bugs.

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
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.