[Differential] D10485: Replace dhcp option 150 by 66

2017-05-02 Thread tsoome (Toomas Soome)
tsoome added a comment. btw, I did test with my vmware fusion VM, the pxe boot is sending out: DHCP: Message type = DHCPDISCOVER DHCP: Requested Options: DHCP:1 (Subnet Mask) DHCP:2 (UTC Time Offset) DHCP:3 (Router) DHCP:5 (IEN 116 Name Servers) DHCP:6 (DNS Ser

[Differential] D10485: Replace dhcp option 150 by 66

2017-05-02 Thread tsoome (Toomas Soome)
tsoome added a comment. In https://reviews.freebsd.org/D10485#219245, @kczekirda wrote: > @rgrimes > Please try to boot CURRENT over tftp protocol and without any third part software like iPXE. > > @tsoome > > > Note that dhcp servers in real life can offer all the configured

[Differential] D10485: Replace dhcp option 150 by 66

2017-05-02 Thread kczekirda (Kamil Czekirda)
kczekirda added a comment. @rgrimes Please try to boot CURRENT over tftp protocol and without any third part software like iPXE. @tsoome > Note that dhcp servers in real life can offer all the configured data. And well, we can process both 66 and 150 just because that data may be

[Bug 218886] ifconfig lagg0 destroy will crash the system

2017-05-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218886 Alan Somers changed: What|Removed |Added CC||loos...@freebsd.org --- Comment #8 f

[Bug 218886] ifconfig lagg0 destroy will crash the system

2017-05-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218886 --- Comment #7 from Lutz Rabing --- Created attachment 182246 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182246&action=edit core.txt.0 -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 218886] ifconfig lagg0 destroy will crash the system

2017-05-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218886 --- Comment #6 from Alan Somers --- Progress! Now try running "crashinfo". Normally that should run automatically, unless you put "crashinfo_enable=NO" in /etc/rc.conf. It could also fail to run if your kernel is stored in a nondefault l

[Bug 218886] ifconfig lagg0 destroy will crash the system

2017-05-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218886 --- Comment #5 from Lutz Rabing --- (In reply to Alan Somers from comment #4) Yes, dumpdev="NO" was set in rc.conf. I changed it to AUTO and repeated the crash. There is just a info.0 and vmcore.0: drwxr-x--- 2 root wheel 8 M

[Bug 218886] ifconfig lagg0 destroy will crash the system

2017-05-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218886 --- Comment #4 from Alan Somers --- Lutz, unfortunately that screenshot doesn't capture anything useful. It seems like your system is not setup to dump core on panic. Could you please check the output of "dumpon -l"? If it's empty, then

[Bug 218886] ifconfig lagg0 destroy will crash the system

2017-05-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218886 --- Comment #3 from Lutz Rabing --- Hi Alan, the /var/crash/ dir is empty. The system appears to be dead immediately. I just have IPMI console access and the error message appears for 0.5s before the BIOS boot screen is shown. I'll attach

[Bug 218886] ifconfig lagg0 destroy will crash the system

2017-05-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218886 --- Comment #2 from Lutz Rabing --- Created attachment 182244 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182244&action=edit crash_screen -- You are receiving this mail because: You are the assignee for the bug.