Jxrgen Birkhaug writes: > > Quoting Malcolm Beattie <[EMAIL PROTECTED]>: > > > > <s> > > > > > > Better make that triple of device numbers start on an even boundary. > > > > > > --Malcolm > <s> > Why?
I'm sure I've seen somewhere that it's a requirement but I can't remember exactly which part of the system requires it and the only reference I can find at the moment is one which only mentions the requirement for OSE and not OSD (i.e. for non-QDIO). However, something does look a bit odd about your new try: > Adapter 0963 Type: HIPER Name: UNASSIGNED Devices: 3 > Port 0 MAC: 00-04-AC-00-00-0C LAN: SYSTEM LNXLAN02 MFS: 16384 > Connection Name: HALLOLE State: Session Established > Device: 0964 Unit: 001 Role: CTL-READ > Device: 0965 Unit: 002 Role: CTL-WRITE > Device: 0963 Unit: 000 Role: DATA Notice that VM shows that the triple of device numbers 963,964,965 have been switched around to the order 964,965,963 in order for the first even number to become the CTL-READ device. The error message from your Linux guest was > qeth: Trying to use card with devnos 0x963/0x964/0x965 > qeth: received an IDX TERMINATE on irq 0x14/0x15 with cause code 0x08 > qeth: IDX_ACTIVATE on read channel irq 0x14: negative reply > qeth: There were problems in hard-setting up the card. and it may be worth checking whether Linux has decided to switch around the device numbers in the same way, perhaps by checking in /proc/subchannels or /proc/chandev whether subchannel 0x14 really is the control read device. On the other hand, it may be simpler just to enforce the "even boundary" constraint, if only to avoid having those permuted device numbers appearing. I guess that there may even be other differences since this time you're using a hipersockets device instead of a qdio one and it'll have a different portname and so on (which is case sensitive and so may be worth checking too: even if your OS/390 people see/quote it in upper case it's possible that the underlying portname could be lower case). Setting up QDIO/Hipersockets connections have quite a few little subtle requirements and getting any of them wrong can lead to the sort of errors you're seeing. It's a bit of nuisance but usually it's just a question of checking every little thing one more time to find the one that you're running into. --Malcolm -- Malcolm Beattie <[EMAIL PROTECTED]> Linux Technical Consultant IBM EMEA Enterprise Server Group... ...from home, speaking only for myself
