Re: Upgrade 6.0 -> 6.1: ix mmba is not mem space

[Stuart Henderson]

On 2018/05/31 15:16, mxb wrote:
> With -stable kernel and modded syspatch I was able to pull down all the 
> patches I needed to have this machine to be fully up to date.

As ever, you get to keep both pieces if it breaks, and please make
sure you mention this if you report any problems :-)

Re: Upgrade 6.0 -> 6.1: ix mmba is not mem space

[mxb]

With -stable kernel and modded syspatch I was able to pull down all the patches 
I needed to have this machine to be fully up to date.

Sent from my iDevice

> 30 мая 2018 г., в 18:59, Stuart Henderson  написал(а):
> 
>> On 2018-05-30, Maxim Bourmistrov  wrote:
>> I ended up with a -stable kernel and syspatch refusing to pull down patches, 
>> but this is another story.
> 
> syspatch is only for releases or systems which have been syspatch'ed directly
> from a release - it can't work with -stable, own-built kernels or kernels 
> modified
> with config(8).
> 
> 

Re: Upgrade 6.0 -> 6.1: ix mmba is not mem space

[Stuart Henderson]

On 2018-05-30, Maxim Bourmistrov  wrote:
> I ended up with a -stable kernel and syspatch refusing to pull down patches, 
> but this is another story.

syspatch is only for releases or systems which have been syspatch'ed directly
from a release - it can't work with -stable, own-built kernels or kernels 
modified
with config(8).

Re: Upgrade 6.0 -> 6.1: ix mmba is not mem space

[Maxim Bourmistrov]

Yepp.
I ended up with a -stable kernel and syspatch refusing to pull down patches, 
but this is another story.
It’s up2date now.
Thanks all.

Br

> 30 maj 2018 kl. 09:36 skrev Peter Hessler :
> 
> Assuming 1.140 is the "problem", 1.151 should fix it.

Re: Upgrade 6.0 -> 6.1: ix mmba is not mem space

[Peter Hessler]

Assuming 1.140 is the "problem", 1.151 should fix it.

AKA: upgrade to 6.3.


On 2018 May 30 (Wed) at 09:21:58 +0200 (+0200), mxb wrote:
:Reverting if_ix.c to rev 1.139 brought ix back to live.
:
:Sent from my iDevice
:
:> 29 мая 2018 г., в 21:36, Maxim Bourmistrov  
написал(а):
:> 
:> Diff, discussed in the thread, seems to follow all the way to 6.3.
:> Sure I probably can try out 6.3, but I have a feeling that this will not 
help.
:> 
:> dmesg can be arranged.
:> 
:> Br 
:> 
:>> 29 maj 2018 kl. 20:56 skrev Chris Cappuccio :
:>> 
:>> No magic expected here, but why not try 6.3? 6.1 is not supported anymore, 
and in any event, you need to include full dmesg so that others without DL360 
Gen9 have a chance at helping you.
:>> 
:>> Maxim Bourmistrov [m...@alumni.chalmers.se] wrote:
:>>> Hey,
:>>> While moving one of machines from 6.0 to 6.1, I found 6.1 not able to 
attach ix-device.
:>>> Machine is HP DL360 Gen9.
:>>> 
:>>> ix0 at pci5 dev 0 function 0 "Intel 82599" rev 0x01: mmba is not mem space
:>>> ix1 at pci5 dev 0 function 1 "Intel 82599" rev 0x01: mmba is not mem space
:>>> 
:>>> Found this thread
:>>> 
http://openbsd-archive.7691.n7.nabble.com/OpenBSD-6-1-ix-Intel-82598EB-issue-td317072.html
 

:>>> 
:>>> and as far as I can see, this diff is in tree, but not helping here :(
:>>> 
:>>> Any clues? 
:>>> 
:>>> 4:0:1: Intel 82599
:>>>  0x: Vendor ID: 8086 Product ID: 10fb
:>>>  0x0004: Command: 0147 Status: 0010
:>>>  0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 01
:>>>  0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 10
:>>>  0x0010: BAR mem 32bit addr: 0x92c0/0x0010
:>>>  0x0014: BAR empty ()
:>>>  0x0018: BAR io addr: 0x2000/0x0020
:>>>  0x001c: BAR mem 32bit addr: 0x92e0/0x4000
:>>>  0x0020: BAR empty ()
:>>>  0x0024: BAR empty ()
:>>>  0x0028: Cardbus CIS: 
:>>>  0x002c: Subsystem Vendor ID: 103c Product ID: 17d0
:>>>  0x0030: Expansion ROM Base Address: 
:>>>  0x0038: 
:>>>  0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00
:>>>  0x0040: Capability 0x01: Power Management
:>>>  State: D0 PME# enabled
:>>>  0x0050: Capability 0x05: Message Signalled Interrupts (MSI)
:>>>  0x0070: Capability 0x11: Extended Message Signalled Interrupts (MSI-X)
:>>>  0x00a0: Capability 0x10: PCI Express
:>>>  Link Speed: 5.0 / 5.0 GT/s Link Width: x8 / x8
:>>>  0x0100: Enhanced Capability 0x01: Advanced Error Reporting
:>>>  0x0140: Enhanced Capability 0x03: Device Serial Number
:>>>  0x0150: Enhanced Capability 0x0e: Alternate Routing ID
:>>>  0x0160: Enhanced Capability 0x10: Single Root I/O Virtualization
:>>>  0x00e0: Capability 0x03: Vital Product Data (VPD)
:>>> 
:>>> Br
:>>> 
:>>> 
:> 
:

-- 
Democracy can learn some things from Communism: for example, when a
Communist politician is through, he is through.

Re: Upgrade 6.0 -> 6.1: ix mmba is not mem space

[mxb]

Reverting if_ix.c to rev 1.139 brought ix back to live.

Sent from my iDevice

> 29 мая 2018 г., в 21:36, Maxim Bourmistrov  
> написал(а):
> 
> Diff, discussed in the thread, seems to follow all the way to 6.3.
> Sure I probably can try out 6.3, but I have a feeling that this will not help.
> 
> dmesg can be arranged.
> 
> Br 
> 
>> 29 maj 2018 kl. 20:56 skrev Chris Cappuccio :
>> 
>> No magic expected here, but why not try 6.3? 6.1 is not supported anymore, 
>> and in any event, you need to include full dmesg so that others without 
>> DL360 Gen9 have a chance at helping you.
>> 
>> Maxim Bourmistrov [m...@alumni.chalmers.se] wrote:
>>> Hey,
>>> While moving one of machines from 6.0 to 6.1, I found 6.1 not able to 
>>> attach ix-device.
>>> Machine is HP DL360 Gen9.
>>> 
>>> ix0 at pci5 dev 0 function 0 "Intel 82599" rev 0x01: mmba is not mem space
>>> ix1 at pci5 dev 0 function 1 "Intel 82599" rev 0x01: mmba is not mem space
>>> 
>>> Found this thread
>>> http://openbsd-archive.7691.n7.nabble.com/OpenBSD-6-1-ix-Intel-82598EB-issue-td317072.html
>>>  
>>> 
>>> 
>>> and as far as I can see, this diff is in tree, but not helping here :(
>>> 
>>> Any clues? 
>>> 
>>> 4:0:1: Intel 82599
>>>  0x: Vendor ID: 8086 Product ID: 10fb
>>>  0x0004: Command: 0147 Status: 0010
>>>  0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 01
>>>  0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 10
>>>  0x0010: BAR mem 32bit addr: 0x92c0/0x0010
>>>  0x0014: BAR empty ()
>>>  0x0018: BAR io addr: 0x2000/0x0020
>>>  0x001c: BAR mem 32bit addr: 0x92e0/0x4000
>>>  0x0020: BAR empty ()
>>>  0x0024: BAR empty ()
>>>  0x0028: Cardbus CIS: 
>>>  0x002c: Subsystem Vendor ID: 103c Product ID: 17d0
>>>  0x0030: Expansion ROM Base Address: 
>>>  0x0038: 
>>>  0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00
>>>  0x0040: Capability 0x01: Power Management
>>>  State: D0 PME# enabled
>>>  0x0050: Capability 0x05: Message Signalled Interrupts (MSI)
>>>  0x0070: Capability 0x11: Extended Message Signalled Interrupts (MSI-X)
>>>  0x00a0: Capability 0x10: PCI Express
>>>  Link Speed: 5.0 / 5.0 GT/s Link Width: x8 / x8
>>>  0x0100: Enhanced Capability 0x01: Advanced Error Reporting
>>>  0x0140: Enhanced Capability 0x03: Device Serial Number
>>>  0x0150: Enhanced Capability 0x0e: Alternate Routing ID
>>>  0x0160: Enhanced Capability 0x10: Single Root I/O Virtualization
>>>  0x00e0: Capability 0x03: Vital Product Data (VPD)
>>> 
>>> Br
>>> 
>>> 
> 

Re: Upgrade 6.0 -> 6.1: ix mmba is not mem space

[Maxim Bourmistrov]

Diff, discussed in the thread, seems to follow all the way to 6.3.
Sure I probably can try out 6.3, but I have a feeling that this will not help.

dmesg can be arranged.

Br 

> 29 maj 2018 kl. 20:56 skrev Chris Cappuccio :
> 
> No magic expected here, but why not try 6.3? 6.1 is not supported anymore, 
> and in any event, you need to include full dmesg so that others without DL360 
> Gen9 have a chance at helping you.
> 
> Maxim Bourmistrov [m...@alumni.chalmers.se] wrote:
>> Hey,
>> While moving one of machines from 6.0 to 6.1, I found 6.1 not able to attach 
>> ix-device.
>> Machine is HP DL360 Gen9.
>> 
>> ix0 at pci5 dev 0 function 0 "Intel 82599" rev 0x01: mmba is not mem space
>> ix1 at pci5 dev 0 function 1 "Intel 82599" rev 0x01: mmba is not mem space
>> 
>> Found this thread
>> http://openbsd-archive.7691.n7.nabble.com/OpenBSD-6-1-ix-Intel-82598EB-issue-td317072.html
>>  
>> 
>> 
>> and as far as I can see, this diff is in tree, but not helping here :(
>> 
>> Any clues? 
>> 
>> 4:0:1: Intel 82599
>>   0x: Vendor ID: 8086 Product ID: 10fb
>>   0x0004: Command: 0147 Status: 0010
>>   0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 01
>>   0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 10
>>   0x0010: BAR mem 32bit addr: 0x92c0/0x0010
>>   0x0014: BAR empty ()
>>   0x0018: BAR io addr: 0x2000/0x0020
>>   0x001c: BAR mem 32bit addr: 0x92e0/0x4000
>>   0x0020: BAR empty ()
>>   0x0024: BAR empty ()
>>   0x0028: Cardbus CIS: 
>>   0x002c: Subsystem Vendor ID: 103c Product ID: 17d0
>>   0x0030: Expansion ROM Base Address: 
>>   0x0038: 
>>   0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00
>>   0x0040: Capability 0x01: Power Management
>>   State: D0 PME# enabled
>>   0x0050: Capability 0x05: Message Signalled Interrupts (MSI)
>>   0x0070: Capability 0x11: Extended Message Signalled Interrupts (MSI-X)
>>   0x00a0: Capability 0x10: PCI Express
>>   Link Speed: 5.0 / 5.0 GT/s Link Width: x8 / x8
>>   0x0100: Enhanced Capability 0x01: Advanced Error Reporting
>>   0x0140: Enhanced Capability 0x03: Device Serial Number
>>   0x0150: Enhanced Capability 0x0e: Alternate Routing ID
>>   0x0160: Enhanced Capability 0x10: Single Root I/O Virtualization
>>   0x00e0: Capability 0x03: Vital Product Data (VPD)
>> 
>> Br
>> 
>> 

Re: Upgrade 6.0 -> 6.1: ix mmba is not mem space

[Chris Cappuccio]

No magic expected here, but why not try 6.3? 6.1 is not supported anymore, and 
in any event, you need to include full dmesg so that others without DL360 Gen9 
have a chance at helping you.

Maxim Bourmistrov [m...@alumni.chalmers.se] wrote:
> Hey,
> While moving one of machines from 6.0 to 6.1, I found 6.1 not able to attach 
> ix-device.
> Machine is HP DL360 Gen9.
> 
> ix0 at pci5 dev 0 function 0 "Intel 82599" rev 0x01: mmba is not mem space
> ix1 at pci5 dev 0 function 1 "Intel 82599" rev 0x01: mmba is not mem space
> 
> Found this thread
> http://openbsd-archive.7691.n7.nabble.com/OpenBSD-6-1-ix-Intel-82598EB-issue-td317072.html
>  
> 
> 
> and as far as I can see, this diff is in tree, but not helping here :(
> 
> Any clues? 
> 
> 4:0:1: Intel 82599
>0x: Vendor ID: 8086 Product ID: 10fb
>0x0004: Command: 0147 Status: 0010
>0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 01
>0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 10
>0x0010: BAR mem 32bit addr: 0x92c0/0x0010
>0x0014: BAR empty ()
>0x0018: BAR io addr: 0x2000/0x0020
>0x001c: BAR mem 32bit addr: 0x92e0/0x4000
>0x0020: BAR empty ()
>0x0024: BAR empty ()
>0x0028: Cardbus CIS: 
>0x002c: Subsystem Vendor ID: 103c Product ID: 17d0
>0x0030: Expansion ROM Base Address: 
>0x0038: 
>0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00
>0x0040: Capability 0x01: Power Management
>State: D0 PME# enabled
>0x0050: Capability 0x05: Message Signalled Interrupts (MSI)
>0x0070: Capability 0x11: Extended Message Signalled Interrupts (MSI-X)
>0x00a0: Capability 0x10: PCI Express
>Link Speed: 5.0 / 5.0 GT/s Link Width: x8 / x8
>0x0100: Enhanced Capability 0x01: Advanced Error Reporting
>0x0140: Enhanced Capability 0x03: Device Serial Number
>0x0150: Enhanced Capability 0x0e: Alternate Routing ID
>0x0160: Enhanced Capability 0x10: Single Root I/O Virtualization
>0x00e0: Capability 0x03: Vital Product Data (VPD)
> 
> Br
> 
> 

Upgrade 6.0 -> 6.1: ix mmba is not mem space

[Maxim Bourmistrov]

Hey,
While moving one of machines from 6.0 to 6.1, I found 6.1 not able to attach 
ix-device.
Machine is HP DL360 Gen9.

ix0 at pci5 dev 0 function 0 "Intel 82599" rev 0x01: mmba is not mem space
ix1 at pci5 dev 0 function 1 "Intel 82599" rev 0x01: mmba is not mem space

Found this thread
http://openbsd-archive.7691.n7.nabble.com/OpenBSD-6-1-ix-Intel-82598EB-issue-td317072.html
 


and as far as I can see, this diff is in tree, but not helping here :(

Any clues? 

4:0:1: Intel 82599
   0x: Vendor ID: 8086 Product ID: 10fb
   0x0004: Command: 0147 Status: 0010
   0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 01
   0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 10
   0x0010: BAR mem 32bit addr: 0x92c0/0x0010
   0x0014: BAR empty ()
   0x0018: BAR io addr: 0x2000/0x0020
   0x001c: BAR mem 32bit addr: 0x92e0/0x4000
   0x0020: BAR empty ()
   0x0024: BAR empty ()
   0x0028: Cardbus CIS: 
   0x002c: Subsystem Vendor ID: 103c Product ID: 17d0
   0x0030: Expansion ROM Base Address: 
   0x0038: 
   0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00
   0x0040: Capability 0x01: Power Management
   State: D0 PME# enabled
   0x0050: Capability 0x05: Message Signalled Interrupts (MSI)
   0x0070: Capability 0x11: Extended Message Signalled Interrupts (MSI-X)
   0x00a0: Capability 0x10: PCI Express
   Link Speed: 5.0 / 5.0 GT/s Link Width: x8 / x8
   0x0100: Enhanced Capability 0x01: Advanced Error Reporting
   0x0140: Enhanced Capability 0x03: Device Serial Number
   0x0150: Enhanced Capability 0x0e: Alternate Routing ID
   0x0160: Enhanced Capability 0x10: Single Root I/O Virtualization
   0x00e0: Capability 0x03: Vital Product Data (VPD)

Br