On 2018-03-09, Holger Glaess <gla...@glaessixs.de> wrote: > hi > > > the problem is not gone. > > > i left the computer for a couple of hours ,then i try to work with hin > but he lost the > > connection . > > > i saw tine re interface with an ip and the outgoing dhcp request by > tcpdump . > > but he is not able to cumunicatate through ethernet. > > i reboot the system , nothing work but he set the ip from the lease db > of the dhclient > > i delete thies and reboot again , nothing. > > > next i reboot the linux , ethernet work > > then i reboot back to openbsd ethernet work ! > > i can do an connect , for example , ssh to an other system > > > there is something wrong .
I would suggest: - Save pcidump -vvxx to a file when it's broken - Check tcpdump on the OpenBSD system with the problem and see if it is RECEIVING anything from the network - If you can run tcpdump on the DHCP server, do that as well (while you run dhclient), see if it can hear anything the OpenBSD system is SENDING on the network - Boot to Linux and back again to hopefully fix it - Save pcidump -vvxx to a different file when it's working - Run "sendbug -P > somefile" as root on the machine where you're having problems to get a report template which will include pcidump, b64-encoded acpi files and dmesg. Edit and fill in a description of the problem, as clear as you can. Include a diff of the two pcidump output files. Read through again and check that it makes sense on its own then send to bugs@.
