Bug 430292 - libdhcp4client dies with "ks=http://<foo>"
libdhcp4client dies with "ks=http://<foo>"
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: dhcp (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: David Cantrell
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-25 14:58 EST by Eric Sandeen
Modified: 2008-03-25 23:09 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-25 23:09:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Eric Sandeen 2008-01-25 14:58:12 EST
Rawhide from a couple/few days ago, when booted with "ks=http://<foo>" dies for
me like this:

loader received SIGSEGV!  Backtrace:                                           
/sbin/loader(loaderSegvHandler+0xa0)[0x8050060]
[0x12f420]
/lib/libdhcp4client-4.0.so.0(state_selecting+0x60)[0x3a2690]
/lib/libdhcp4client-4.0.so.0(process_outstanding_timeouts+0xf8)[0x3aeba8]
/lib/libdhcp4client-4.0.so.0(dhcpv4_client+0x175a)[0x3a450a]
/lib/libdhcp-1.99.so.1(do_dhcpv4+0x3c)[0x32dbbc]
/lib/libdhcp-1.99.so.1[0x32f975]
/lib/libdhcp-1.99.so.1(dhcp_nic+0x3a)[0x32feea]
/lib/libdhcp-1.99.so.1(pumpDhcpClassRun+0x127)[0x337ca7]
/sbin/loader(doDhcp+0x12a)[0x8062c6a]
/sbin/loader(configureTCPIP+0x9b8)[0x8065428]
/sbin/loader(readNetConfig+0x3bd)[0x8065b3d]
/sbin/loader(main+0xd9a)[0x805175a]
/lib/libc.so.6(__libc_start_main+0xe0)[0x5014a0]
/sbin/loader[0x804e121]
install exited abnormally [1/1] 
sending termination signals...done
sending kill signals...done
disabling swap...
unmounting filesystems...
        /proc done
        /dev/pts done
        /sys done
you may safely reboot your system
Comment 1 David Cantrell 2008-03-25 23:09:25 EDT
This should be working in the latest rawhide trees.

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