>>> On 3/12/2009 at 3:37 PM, Alan Altmark <alan_altm...@us.ibm.com> wrote: > On Thursday, 03/12/2009 at 02:40 EDT, Mark Post <mp...@novell.com> wrote: >> > I get an IDX TERMINATE with cause code 0xf6, which I have read some of >> > the archives that said that was a layer2/layer3 mismatch error. >> >> I'm pretty sure that would be a 0x4e error, since I just deliberately > caused >> that mismatch on one of my test systems to check. > > - 0x4E means the adapter doesn't understand what the device driver told > it. Either a bad primitive was sent or the operands are bad. This could > be because you've configured Linux to speak "OSA" but you defined a > "HIPERS" NIC.
I took a working virtual NIC, coupled to a Layer 3 VSWITCH and: - ifconfig eth1 down - echoed a "0" into the online pseudo file for the NIC - echoed "1" into the layer2 pseudo file - echoed "1" into the online pseudo file and got this error: qeth: received an IDX TERMINATE with cause code 0x4e qeth: sense data available on channel 0.0.0700. qeth: cstat 0x0 dstat 0xE qeth: irb: 00 c2 60 17 11 aa 20 38 0e 00 10 00 00 80 00 00 qeth: irb: 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: Recovery of device 0.0.0700 started ... qeth: Initialization in hardsetup failed! rc=-5 I then echoed a "0" into the layer2 pseudo file, and a "1" into the online pseudo file, and it came right back online: qeth: Device 0.0.0700/0.0.0701/0.0.0702 is a Guest LAN QDIO card (level: V519) with link type GuestLAN QDIO (portname: ) qeth: Hardware IP fragmentation not supported on eth1 qeth: VLAN enabled qeth: Multicast enabled qeth: IPV6 enabled qeth: Broadcast enabled qeth: Using SW checksumming on eth1. qeth: Outbound TSO not supported on eth1 eth1: no IPv6 routers present So, I have to say my empirical evidence shows that a 0x4e can be the result of a layer mismatch between the driver and the VSWITCH. > - 0xF6 means the adapter understood the instruction, but it's not > compatible with the underlying LAN type (L2/L3) I guess we have to wait some more for the qeth driver to put out error messages with these codes interpreted for us. Maybe someone can make a pass through Boeblingen with some sort of motivator. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
