Opened 5 years ago

Closed 5 years ago

#1237 closed defect (worksforme)

segfault issues after upgrading to 7.0-1

Reported by: Fer Owned by:
Priority: major Milestone:
Component: smartctl Version: 7.0
Keywords: Cc:


After upgrade to 7.0-1 these messages started to appear everytime I run smartctl.

I had to downgrade to 6.5 and issues dissapear. Any clues?

[vie sep 20 20:45:27 2019] smartctl[29739]: segfault at 7ffedea138ac ip 00007fb580c49aa9 sp 00007ffedea0f8d8 error 4 in[7fb580af5000+1c3000]
[vie sep 20 20:45:27 2019] smartctl[29742]: segfault at 7ffd789ae000 ip 00007f52fb59cb10 sp 00007ffd789aa608 error 4 in[7f52fb448000+1c3000]
[vie sep 20 20:45:27 2019] smartctl[29745]: segfault at 7ffd86dc2000 ip 00007f68b8b3db20 sp 00007ffd86dbe7e8 error 4 in[7f68b89e9000+1c3000]
[vie sep 20 20:45:27 2019] smartctl[29754]: segfault at 7ffe88d7c000 ip 00007f9a6668eb48 sp 00007ffe88d78418 error 4 in[7f9a6653a000+1c3000]
[vie sep 20 20:45:28 2019] smartctl[29763]: segfault at 7ffcf70b3000 ip 00007fa0493fab48 sp 00007ffcf70af218 error 4 in[7fa0492a6000+1c3000]
[vie sep 20 20:45:29 2019] smartctl[29780]: segfault at 7ffcaf8f329c ip 00007f194eebbaa9 sp 00007ffcaf8ef2c8 error 4 in[7f194ed67000+1c3000]
[vie sep 20 20:45:29 2019] smartctl[29783]: segfault at 7ffee6f07000 ip 00007f2c099b9b38 sp 00007ffee6f03338 error 4 in[7f2c09865000+1c3000]
[root@zxxx300 ~]# uname -a
Linux zxxx300 3.10.0-1062.1.1.el7.x86_64 #1 SMP Fri Sep 13 22:55:44 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Change History (2)

comment:1 by Christian Franke, 5 years ago

Keywords: segfault removed
Milestone: Release 7.1undecided

Many Linux distros provide 7.0 and no similar reports exists, so please be more specific:

  • Distribution?
  • smartctl command line which produces these segfaults?
  • smartctl -V output?
  • Does smartd produce similar segfaults?

PS: Please do not set the Milestone in future submissions.

comment:2 by Christian Franke, 5 years ago

Milestone: undecided
Resolution: worksforme
Status: newclosed

Problem could not be reproduced. Reporter did not provide requested information.

Note: See TracTickets for help on using tickets.