Re: 5.8-stable: lang/python/2.7 -tkinter

[Adam Jensen]

On Sat, 2 Apr 2016 08:24:19 +0200
Remi Pointel  wrote:

> 
> Hello,
> 
> Tkinter has been renamed to tkinter in Python 3, so you should import 
> 'Tkinter' in Python 2 (https://docs.python.org/2/library/tkinter.html).
> 
> Cheers,
> 
> Remi.

Thanks, Remi. That fixes the problem. I feel a bit goofy for not doing the 
basic research before posting to ports-bugs.

Re: em0 stops working after random amount of time in OpenBSD 5.8/5.9

[Mischa]

Hi Evgeniy,

Thank you for your suggestion. Unfortunately there is already a card in the 
only available slot.
I did notice that the network cards had a different chipset.

em0 at pci4 dev 0 function 0 "Intel 82573E" rev 0x03: msi, address 
00:30:48:96:42:06
em1 at pci5 dev 0 function 0 "Intel 82573L" rev 0x00: msi, address 
00:30:48:96:42:07

I moved the cable em1 and it's been behaving as expected since.

Thanx for responding!!

Mischa

> On 03 Apr 2016, at 02:13, Evgeniy Sudyr  wrote:
> 
> Mischa, please provide sendbug (1) with all details to developers and
> then wait and hope someone will pick that bug.
> 
> Personally I will suggest you to don't use that 11 years old NIC which
> causes such problems (in archives I found some reports similar to
> yours) and get better NIC which fits your needs.
> 
> Check Intel i350
> http://www.intel.com/content/www/us/en/embedded/products/networking/ethernet-controller-i350-datasheet.html
> 
> You can get it for ~ $150 retail price (dual port). I never had issues
> with this one, also I didn't used even half of it's cool features on
> any platform.
> 
> 
> On Sat, Apr 2, 2016 at 10:14 PM, Mischa Peters  wrote:
>> Hi Evgeniy,
>> 
>> One of the questions I had was indeed how to troubleshoot this. Nothing is 
>> in dmesg or messages that is out of the ordinary, I can not find anything 
>> that changes on the interface or netstat.
>> 
>> Until the 18th of March this machine was running FreeBSD, without any 
>> issues. I moved from 9.3-RELEASE-pXX to OpenBSD 5.8. There are still 2 
>> machines of the same type that are running FreeBSD 9.3 without any issues.
>> 
>> I do know there are issues in FreeBSD 10 with this NIC which haven't been 
>> resolved. But they have primarily to do that the driver is not loading.
>> 
>> The thing that is strange is that it works after reboot, I can ping an IP. 
>> But as soon as I run ftp or pkg_add for example, it stops working.
>> 
>> Mischa
>> 
>> --
>> 
>> 
>> 
>> --
>>> On 02 Apr 2016, at 21:15, Evgeniy Sudyr  wrote:
>>> 
>>> Mischa,
>>> 
>>> 1) Consider using sendbug (1) to provide report (read section saying
>>> "The following items should be contained in every bug report")
>>> 
>>> http://www.openbsd.org/report.html
>>> 
>>> 2) I suggest to provide more details about your system configuration.
>>> Most interesting is if any sysctl tuning done and if it was working
>>> system or new/fresh setup which never worked before?
>>> 
>>> 3) Can it be some broken hardware? I just googled for your board / NIC
>>> and both are about 9yrs old.
>>> 
>>> --
>>> Evgeniy
>>> 
 On Sat, Apr 2, 2016 at 7:36 PM, Mischa  wrote:
 Hi All,
 
 I just tried with: OpenBSD host 5.9 GENERIC.MP#1888 amd64
 The result is still the same. Networking stops and sometimes continues 
 after some time.
 Could this because of SMP networking?
 
 What I am seeing on the switch is that the MAC address is still in the MAC 
 table.
 But there is no longer an ARP entry.
 
 Mischa
 
 
> On 22 Mar 2016, at 12:18, Mischa  wrote:
> 
> Hi All,
> 
> I would be happy to provide remote console access if that helps.
> 
> Mischa
> 
>> On 20 Mar 2016, at 14:52, Mischa  wrote:
>> 
>> Hi All,
>> 
>> I am running OpenBSD 5.8, and tried 5.9 as well, on a SuperMicro PDSMi 
>> which has an Intel 82573E.
>> For some reason networking just stops working after a random amount of 
>> time and usually happens when I SSH-ed into the machine.
>> When connected to the console it seems to be working longer. I am 
>> testing this by pinging an IP address on the local subnet.
>> 
>> Unfortunately I can not find anything different from an interface 
>> perspective, subnet perspective and nothing appears in the logs.
>> The problem goes away, temporarily, when I bounce the interface on the 
>> switch.
>> 
>> How can I best troubleshoot the cause?
>> 
>> # dmesg
>> em0 at pci4 dev 0 function 0 "Intel 82573E" rev 0x03: msi, address 
>> 00:30:48:96:42:06
>> 
>> # pcidump -v
>> 13:0:0: Intel 82573E
>>   0x: Vendor ID: 8086 Product ID: 108c
>>   0x0004: Command: 0107 Status: 0010
>>   0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 03
>>   0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 10
>>   0x0010: BAR mem 32bit addr: 0xe8a0/0x0002
>>   0x0014: BAR empty ()
>>   0x0018: BAR io addr: 0x5000/0x0020
>>   0x001c: BAR empty ()
>>   0x0020: BAR empty ()
>>   0x0024: BAR empty ()
>>   0x0028: Cardbus CIS: 
>>   0x002c: Subsystem Vendor ID: 15d9 Product ID: 108c
>>   0x0030: Expansion ROM Base Address: 
>>   0x0038: 
>>   0x003c: Interrupt Pin: 01 Line: