kmod crashed with SIGABRT in raise() when try to modprobe freshly compiled nvidia experimental 310 driver (same case with ALL other nvidia prop drivers)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kmod (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Fresh ubuntu 13.04 installation with live cd of 28/01/12 need of nvidia graphics driver for GeForce GT 610.
Building only for 3.8.0-2-generic
Building for architecture x86_64
Building initial module for 3.8.0-2-generic
Done.
nvidia_
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/
depmod.....
DKMS: install completed.
python-xkit (0.5.0ubuntu1) wird eingerichtet ...
screen-
nvidia-
update-
Trigger für bamfdaemon werden verarbeitet ...
Rebuilding /usr/share/
Trigger für initramfs-tools werden verarbeitet ...
update-initramfs: Generating /boot/initrd.
modprobe: ../tools/
Aborted (core dumped)
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: kmod 9-2ubuntu6
ProcVersionSign
Uname: Linux 3.8.0-2-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Tue Jan 29 09:38:35 2013
ExecutablePath: /bin/kmod
InstallationDate: Installed on 2013-01-29 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130127)
MarkForUpload: True
ProcCmdline: modprobe --set-version=
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: kmod
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
?? () from /lib/x86_
__assert_fail () from /lib/x86_
?? ()
Title: kmod crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1097462, 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.