Comment 13 for bug 1534345

Revision history for this message
Will Buckner (willbuckner) wrote :

And I should also point out that ifquery is crashing on boot most of the time on these systems:

xxx.log:[ 3.909680] ifquery[378]: segfault at 1 ip 0000000000403187 sp 00007fff7078d8c0 error 4 in ifup[400000+d000]
xxx.log:[ 3.008003] ifquery[380]: segfault at 1 ip 0000000000403187 sp 00007ffdf6935bc0 error 4 in ifup[400000+d000]
xxx.log:[ 2.647084] ifquery[370]: segfault at 1 ip 0000000000403187 sp 00007ffda45292f0 error 4 in ifup[400000+d000]
xxx.log:[ 2.868947] ifquery[370]: segfault at 1 ip 0000000000403187 sp 00007ffcd9140230 error 4 in ifup[400000+d000]
xxx.log:[ 2.846450] ifquery[398]: segfault at 1 ip 0000000000403187 sp 00007ffc5da3d670 error 4 in ifup[400000+d000]
xxx.log:[ 3.070464] ifquery[372]: segfault at 1 ip 0000000000403187 sp 00007fff78691b90 error 4 in ifup[400000+d000]

But I've been unable to get a coredump and it doesn't save a .crash and I can't reproduce it once the system is online. And this "checkport" utility couldn't possibly be running so early in boot--it's triggered by a web request and represents a relatively low percentage of traffic. It's unlikely that it would be triggered at all in the first 30 seconds after boot.