devkit-disks-daemon assert failure: devkit-disks-daemon: atasmart.c:2725: sk_disk_set_blob: Assertion `blob' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devicekit-disks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: devicekit-disks
all i know is i updated to version 64 bit 10/09 and thins keep crashing
ProblemType: Crash
Architecture: amd64
AssertionMessage: devkit-
CrashCounter: 1
CurrentDmesg:
[ 18.911407] usplash:333 freeing invalid memtype ffffffffe000000
[ 25.480027] eth0: no IPv6 routers present
[ 85.500024] Clocksource tsc unstable (delta = -164440784 ns)
[ 1856.160141] usb 1-2: reset high speed USB device using ehci_hcd and address 2
Date: Sat Oct 31 17:10:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
Lsusb:
Bus 001 Device 002: ID 0bc2:3000 Seagate RSS LLC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
NonfreeKernelMo
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: root=UUID=
ProcCmdline: /usr/lib/
ProcEnviron:
ProcVersionSign
Signal: 6
SourcePackage: devicekit-disks
StacktraceTop:
raise () from /lib/libc.so.6
abort () from /lib/libc.so.6
__assert_fail () from /lib/libc.so.6
sk_disk_set_blob () from /lib/libatasmar
?? ()
Title: devkit-disks-daemon assert failure: devkit-
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:
dmi.bios.date: 03/22/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: M61SME-S2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSof
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 #449446, 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.