Bug 2075734 - [RHEL-8] lldpad[1264]: segfault at 0 ip 000055930e66087e sp 00007fffbed583c0 error 6 in lldpad[55930e644000+61000]
Summary: [RHEL-8] lldpad[1264]: segfault at 0 ip 000055930e66087e sp 00007fffbed583c0 ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lldpad
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Aaron Conole
QA Contact: Matt Lucius
URL:
Whiteboard:
Depends On:
Blocks: 2215428
TreeView+ depends on / blocked
 
Reported: 2022-04-15 03:05 UTC by zguo
Modified: 2023-07-07 14:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2215428 (view as bug list)
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
lldpad core file (78.98 KB, application/octet-stream)
2022-09-15 19:16 UTC, Mike Marciniszyn
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-119045 0 None None None 2022-04-15 03:08:07 UTC

Comment 2 Mike Marciniszyn 2022-07-05 17:56:39 UTC
We are currently something similar with the Intel 100g Ethernet adapter:

        lldpad[5287]: segfault at 0 ip 00005603b921c87e sp 00007fff5d898960 error 6 in lldpad[5603b9200000+61000]

The version of lldpad is lldpad-1.0.1-16.git036e314.el8.x86_64.

Trying to get a core file and stack.

Comment 3 Mike Marciniszyn 2022-09-15 19:16:37 UTC
Created attachment 1912203 [details]
lldpad core file

Comment 4 Mike Marciniszyn 2022-09-15 19:17:36 UTC
I have attached a core file.

It doesn't appear much help:
Core was generated by `/usr/sbin/lldpad -t'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000557244f07e6e in ?? ()
(gdb) where
#0  0x0000557244f07e6e in ?? ()
#1  0x00007ffd454c7830 in ?? ()
#2  0xe39af8036bf84d00 in ?? ()
#3  0x00007ffdcb07e080 in ?? ()
#4  0x00005572454c7830 in ?? ()
#5  0x00007ffdcb07decc in ?? ()
#6  0x0000557244f08256 in ?? ()
#7  0x0000000000000000 in ?? ()


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