Bug 590649 - [abrt] crash in hdparm-9.16-3.2.el6: get_dev_geometry: Process /sbin/hdparm was killed by signal 8 (SIGFPE)
Summary: [abrt] crash in hdparm-9.16-3.2.el6: get_dev_geometry: Process /sbin/hdparm w...
Status: CLOSED DUPLICATE of bug 588686
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: hdparm
Version: 6.0
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Karsten Hopp
QA Contact: qe-baseos-daemons
Whiteboard: abrt_hash:22aaa23fbe89bc81b062ad6c586...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-10 12:15 UTC by Jiri Moskovcak
Modified: 2015-02-01 22:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-10 14:53:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
File: backtrace (11.71 KB, text/plain)
2010-05-10 12:15 UTC, Jiri Moskovcak
no flags Details

Description Jiri Moskovcak 2010-05-10 12:15:13 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /sbin/hdparm -g /dev/dm-0
component: hdparm
crash_function: get_dev_geometry
executable: /sbin/hdparm
global_uuid: 22aaa23fbe89bc81b062ad6c58675ce3430e6400
kernel: 2.6.32-23.el6.x86_64
package: hdparm-9.16-3.2.el6
rating: 4
reason: Process /sbin/hdparm was killed by signal 8 (SIGFPE)
release: Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)
How to reproduce: Don't know, it just crashes in background..

Comment 1 Jiri Moskovcak 2010-05-10 12:15:15 UTC
Created attachment 412813 [details]
File: backtrace

Comment 3 RHEL Program Management 2010-05-10 13:24:12 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 4 Karsten Hopp 2010-05-10 14:53:01 UTC

*** This bug has been marked as a duplicate of bug 588686 ***

Note You need to log in before you can comment on or make changes to this bug.