[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Hercules Bus Error



I have been doing a lot of qeth testing both layer2 and layer3 and 
have run into a problem when using the iface parameter on the qeth
definition.

My host environment is debian stable using an updated kernel 
linux-3.12.1-amd64

Hercules is version 4.0 from the github/hyperion repository and I used

configure --enable-debug --prefix= ...... to generate hercules

My guest is debian-390 testing, the only addition is the s390-tools from the IBM
DeveloperWorks website, because the debian version is incomplete for 
some reason!!!

My comms devices are:

#0440.2   CTCI   tun2                                                          
0440.2   CTCI   192.168.200.1 192.168.200.2                                    

#0F40.3   QETH   ipaddr 192.168.10.100 debug                                   
0F40.3   QETH   iface tun2 debug                          

I initially installed the guest with the vCTC, installed the 
correct s390-tools, then used znetconf -a 0f40 -o layer2=0 to set
up the layer3 qeth device. at which point hercules stops with a Bus Error.

I set the tun2 device up on the host side with the ip command
as follows:

ip tuntap add dev tun2 mode tun
ip link set tun2 up
ip addr add 192.168.100.100 peer 192.168.100.50 dev tun2

The ip addr list then shows 

23: tun2: <NO-CARRIER,POINTOPOINT,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast
state DOWN qlen 500
    link/none 
    inet 192.168.100.100 peer 192.168.100.50/32 scope global tun2
       valid_lft forever preferred_lft forever

To validate the tun2 devices I tried to use it for the vCTC connection, 
and it is recognized as a valid device 

Tun2 before hercules starts:

23: tun2: <NO-CARRIER,POINTOPOINT,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 500
    link/none 
    inet 192.168.100.100 peer 192.168.100.50/32 scope global tun2
       valid_lft forever preferred_lft forever

Hercules displays as it starts up:

HHC02198I Device 0440 type 3088 subchannel 0:0004 attached                         
HHC00901I 0:0440 CTCI: interface tun2, type TUN opened                             
HHC02198I Device 0441 type 3088 subchannel 0:0005 attached 

Tun2 after hercules acquires it:

23: tun2: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 500
    link/none 
    inet 192.168.100.100 peer 192.168.100.50/32 scope global tun2
       valid_lft forever preferred_lft forever

I'm not a c programmer but as far as I can see the same code 
is used to open tun2 for both qeth and vCTC.

I have both the run log and a screen print of the last screen 
displayed by hercules before it stops.

Let me know what else you need from me.

Dave Clements.

Reply to: