Re: hipersockets don't come up after HW upgrade
That worked - the error msg. went away, and it shaved about 20 seconds off the boot time. This was a new clone of SLES11sp1. So the file must have been created by yast or something else I did while trying to fix the problem. Since you're paying taxes in Germany, I suppose you're doing your part to fix the other crisis and we appreciate that, too. Best Regards Roger Evans, Autodata Norge A/S http://www.autodata.no On Tue, 2011-11-08 at 13:18 +0100, Ursula Braun wrote: > Roger, > > good news. I am working in the networking team of Linux on System z > development; thus qeth-related problems are my daily business. But > please do not ask me financial questions ;-) > > For your remaining problem: Have you upgraded your system from SLES10? > In this case you may still have old configuration > files /etc/sysconfig/hardware/hwcfg-hsi-bus-ccw-0.0.7000 > or /etc/sysconfig/network/ifcfg-hsi-bus-ccw-0.0.7000. Those are no > longer needed for SLES11 and can be removed. > > Ursula > > On Tue, 2011-11-08 at 12:58 +0100, Roger Evans wrote: > > Thank you, Ursula > > That solved the problem. I can now ping and ftp between my layer3 > > hipersockets. I still get the "Waiting for mandatory devices. > > hsi-bus-ccw-0.0.7000 No interface found " msg. when booting > > but now that it works, I'll just stop watching. > > > > You're pretty amazing. Think you could fix the Greek deficit crisis, > > too? > > > > > > Best Regards > > Roger Evans, > > Autodata Norge A/S > > http://www.autodata.no > > > > -- > 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 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Roger, good news. I am working in the networking team of Linux on System z development; thus qeth-related problems are my daily business. But please do not ask me financial questions ;-) For your remaining problem: Have you upgraded your system from SLES10? In this case you may still have old configuration files /etc/sysconfig/hardware/hwcfg-hsi-bus-ccw-0.0.7000 or /etc/sysconfig/network/ifcfg-hsi-bus-ccw-0.0.7000. Those are no longer needed for SLES11 and can be removed. Ursula On Tue, 2011-11-08 at 12:58 +0100, Roger Evans wrote: > Thank you, Ursula > That solved the problem. I can now ping and ftp between my layer3 > hipersockets. I still get the "Waiting for mandatory devices. > hsi-bus-ccw-0.0.7000 No interface found " msg. when booting > but now that it works, I'll just stop watching. > > You're pretty amazing. Think you could fix the Greek deficit crisis, > too? > > > Best Regards > Roger Evans, > Autodata Norge A/S > http://www.autodata.no > -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Thank you, Ursula That solved the problem. I can now ping and ftp between my layer3 hipersockets. I still get the "Waiting for mandatory devices. hsi-bus-ccw-0.0.7000 No interface found " msg. when booting but now that it works, I'll just stop watching. You're pretty amazing. Think you could fix the Greek deficit crisis, too? Best Regards Roger Evans, Autodata Norge A/S http://www.autodata.no On Tue, 2011-11-08 at 12:22 +0100, Ursula Braun wrote: > Roger, > > get rid of the LLADDR='00:00:00:00:00:00' definition. ifup does no > longer work for a zero MAC-address. HiperSockets define a MAC-address; > during initialization Linux determines this MAC-address and uses it, if > LLADDR is not defined. > > Ursula > > On Tue, 2011-11-08 at 10:47 +0100, Roger Evans wrote: > > Forgot to send the info you requested: > > > > DPRODDB2:/etc/sysconfig/network # cat ifcfg-hsi0 > > BOOTPROTO='static' > > BROADCAST='' > > ETHTOOL_OPTIONS='' > > IPADDR='10.5.2.11/16' > > LLADDR='00:00:00:00:00:00' > > MTU='' > > NAME='Hipersocket (0.0.7000)' > > NETWORK='' > > REMOTE_IPADDR='' > > STARTMODE='manual' > > USERCONTROL='no' > > > > Roger > > > > -- > 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 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Roger, when configuring a network interface with yast, a udev-rule is created for the device containing qeth attribute definitions, among them attribute layer2. Look into /etc/udev/rules.d and check a rule starting with 51-...7000... . I assume this rule contains a line with layer2=1. Change this into layer2=0 and the device should come up with layer3 after reboot. Ursula On Tue, 2011-11-08 at 10:45 +0100, Roger Evans wrote: > THanks for that tip. I can't remember having chosen level2, but I see > that my other (older) interfaces are not level2, so, yes, I would like > to switch to level3. > > I used the commands (from "Device Drivers, Features...") to to take the > device offline and to make it not level2 (level2=9); After that, lsqeth > showed it as level2=0. > But after rebooting, it reverted to level2=1. > > I noticed the following message on VM when booting: > --- > ..skippedWaiting for mandatory devices: hsi-bus-ccw-0.0.7000 __NSC__ > 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 > 3 2 1 0 > > hsi-bus-ccw-0.0.7000No interface found > > > Any idea what I'm missing? > > Roger > -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Roger, get rid of the LLADDR='00:00:00:00:00:00' definition. ifup does no longer work for a zero MAC-address. HiperSockets define a MAC-address; during initialization Linux determines this MAC-address and uses it, if LLADDR is not defined. Ursula On Tue, 2011-11-08 at 10:47 +0100, Roger Evans wrote: > Forgot to send the info you requested: > > DPRODDB2:/etc/sysconfig/network # cat ifcfg-hsi0 > BOOTPROTO='static' > BROADCAST='' > ETHTOOL_OPTIONS='' > IPADDR='10.5.2.11/16' > LLADDR='00:00:00:00:00:00' > MTU='' > NAME='Hipersocket (0.0.7000)' > NETWORK='' > REMOTE_IPADDR='' > STARTMODE='manual' > USERCONTROL='no' > > Roger > -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Forgot to send the info you requested: DPRODDB2:/etc/sysconfig/network # cat ifcfg-hsi0 BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='10.5.2.11/16' LLADDR='00:00:00:00:00:00' MTU='' NAME='Hipersocket (0.0.7000)' NETWORK='' REMOTE_IPADDR='' STARTMODE='manual' USERCONTROL='no' Roger On Tue, 2011-11-08 at 09:37 +0100, Ursula Braun wrote: > Hi Roger, > > your boot.messages do not show any message refering to 0.0.7000 or hsi0. > Your hsi0-device is in state SOFTSETUP, which means it has been > activated successfully; just the ifup step fails. The configuration file > for ifup is /etc/sysconfig/network/ifcfg-hsi0. Can you check the > definitions of this file? > > By the way, you have chosen layer2=1 for your hsi0-device. This is ok, > but it allows communication to other layer2 HiperSockets participants > only, no layer3 HiperSockets participants. > > Regards, Ursula Braun, IBM Germany > > On Tue, 2011-11-08 at 08:39 +0100, Roger Evans wrote: > > Hi, Ursula > > > > uname -a > > Linux DPRODDB2 2.6.32.46-0.3-default #1 SMP 2011-09-29 17:49:31 +0200 > > s390x s390x s390x GNU/Linux > > > > lsqeth > > ... [other devices] > > Device name : hsi0 > > - > > card_type : HiperSockets > > cdev0 : 0.0.7000 > > cdev1 : 0.0.7001 > > cdev2 : 0.0.7002 > > chpid : F1 > > online : 1 > > portname: no portname required > > portno : 0 > > state : SOFTSETUP > > priority_queueing : always queue 2 > > buffer_count: 16 > > layer2 : 1 > > isolation : none > > > > I am attaching the results of the dmesg command > > > > > > Med vennlig hilsen > > > > Roger Evans > > -- > 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 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
THanks for that tip. I can't remember having chosen level2, but I see that my other (older) interfaces are not level2, so, yes, I would like to switch to level3. I used the commands (from "Device Drivers, Features...") to to take the device offline and to make it not level2 (level2=9); After that, lsqeth showed it as level2=0. But after rebooting, it reverted to level2=1. I noticed the following message on VM when booting: --- ..skippedWaiting for mandatory devices: hsi-bus-ccw-0.0.7000 __NSC__ 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 hsi-bus-ccw-0.0.7000No interface found Any idea what I'm missing? Roger On Tue, 2011-11-08 at 09:37 +0100, Ursula Braun wrote: > Hi Roger, > > your boot.messages do not show any message refering to 0.0.7000 or hsi0. > Your hsi0-device is in state SOFTSETUP, which means it has been > activated successfully; just the ifup step fails. The configuration file > for ifup is /etc/sysconfig/network/ifcfg-hsi0. Can you check the > definitions of this file? > > By the way, you have chosen layer2=1 for your hsi0-device. This is ok, > but it allows communication to other layer2 HiperSockets participants > only, no layer3 HiperSockets participants. > > Regards, Ursula Braun, IBM Germany > > On Tue, 2011-11-08 at 08:39 +0100, Roger Evans wrote: > > Hi, Ursula > > > > uname -a > > Linux DPRODDB2 2.6.32.46-0.3-default #1 SMP 2011-09-29 17:49:31 +0200 > > s390x s390x s390x GNU/Linux > > > > lsqeth > > ... [other devices] > > Device name : hsi0 > > - > > card_type : HiperSockets > > cdev0 : 0.0.7000 > > cdev1 : 0.0.7001 > > cdev2 : 0.0.7002 > > chpid : F1 > > online : 1 > > portname: no portname required > > portno : 0 > > state : SOFTSETUP > > priority_queueing : always queue 2 > > buffer_count: 16 > > layer2 : 1 > > isolation : none > > > > I am attaching the results of the dmesg command > > > > > > Med vennlig hilsen > > > > Roger Evans > > -- > 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 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Hi Roger, your boot.messages do not show any message refering to 0.0.7000 or hsi0. Your hsi0-device is in state SOFTSETUP, which means it has been activated successfully; just the ifup step fails. The configuration file for ifup is /etc/sysconfig/network/ifcfg-hsi0. Can you check the definitions of this file? By the way, you have chosen layer2=1 for your hsi0-device. This is ok, but it allows communication to other layer2 HiperSockets participants only, no layer3 HiperSockets participants. Regards, Ursula Braun, IBM Germany On Tue, 2011-11-08 at 08:39 +0100, Roger Evans wrote: > Hi, Ursula > > uname -a > Linux DPRODDB2 2.6.32.46-0.3-default #1 SMP 2011-09-29 17:49:31 +0200 > s390x s390x s390x GNU/Linux > > lsqeth > ... [other devices] > Device name : hsi0 > - > card_type : HiperSockets > cdev0 : 0.0.7000 > cdev1 : 0.0.7001 > cdev2 : 0.0.7002 > chpid : F1 > online : 1 > portname: no portname required > portno : 0 > state : SOFTSETUP > priority_queueing : always queue 2 > buffer_count: 16 > layer2 : 1 > isolation : none > > I am attaching the results of the dmesg command > > > Med vennlig hilsen > > Roger Evans -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Hi, Ursula uname -a Linux DPRODDB2 2.6.32.46-0.3-default #1 SMP 2011-09-29 17:49:31 +0200 s390x s390x s390x GNU/Linux lsqeth ... [other devices] Device name : hsi0 - card_type : HiperSockets cdev0 : 0.0.7000 cdev1 : 0.0.7001 cdev2 : 0.0.7002 chpid : F1 online : 1 portname: no portname required portno : 0 state : SOFTSETUP priority_queueing : always queue 2 buffer_count: 16 layer2 : 1 isolation : none I am attaching the results of the dmesg command Med vennlig hilsen Roger Evans On Mon, 2011-11-07 at 16:53 +0100, Ursula Braun wrote: > Roger, > > the minimum SLES11 SP1 kernel level should be 2.6.32.29-0.3.1. If you > still have problems with a kernel level greater or equal to this one, > something else is wrong. Which qeth-related messages show up in dmesg? > What does "lsqeth" return? > > Regards, Ursula Braun, IBM Germany > > On Mon, 2011-11-07 at 16:04 +0100, Roger Evans wrote: > > Thank you Ursula > > > > I don't seem to have the permissions to read those bugzilla entries, or > > maybe I'm looking in the wrong Novell Bugzilla. > > > > Upgrading from sp3 to sp4 solved the problem for SLES10. > > > > I upgraded my SLES11sp1 with all the upgrades SuSE provides, but still > > get the following msg: > > -- > > DPRODDB2:~ # ifup hsi0 > > hsi0 name: Hipersocket (0.0.7000) > > RTNETLINK answers: Unknown error 18446744073709486085 > > Cannot enable interface hsi0. > > interface hsi0 is not up > > - > > > > I will go through the steps in the hipersocket configuration > > instructions again. Maybe it's not enough to define it in YAST.. > > > > -- > 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 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.32.46-0.3-default (geeko@buildhost) (gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) ) #1 SMP 2011-09-29 17:49:31 +0200 setup.1a06a7: Linux is running as a z/VM guest operating system in 64-bit mode Zone PFN ranges: DMA 0x -> 0x0008 Normal 0x0008 -> 0x0010 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0: 0x -> 0x0010 On node 0 totalpages: 1048576 DMA zone: 7168 pages used for memmap DMA zone: 0 pages reserved DMA zone: 517120 pages, LIFO batch:31 Normal zone: 7168 pages used for memmap Normal zone: 517120 pages, LIFO batch:31 PERCPU: Embedded 11 pages/cpu @8408 s12544 r8192 d24320 u65536 pcpu-alloc: s12544 r8192 d24320 u65536 alloc=16*4096 pcpu-alloc: [0] 00 [0] 01 [0] 02 [0] 03 [0] 04 [0] 05 [0] 06 [0] 07 pcpu-alloc: [0] 08 [0] 09 [0] 10 [0] 11 [0] 12 [0] 13 [0] 14 [0] 15 pcpu-alloc: [0] 16 [0] 17 [0] 18 [0] 19 [0] 20 [0] 21 [0] 22 [0] 23 pcpu-alloc: [0] 24 [0] 25 [0] 26 [0] 27 [0] 28 [0] 29 [0] 30 [0] 31 pcpu-alloc: [0] 32 [0] 33 [0] 34 [0] 35 [0] 36 [0] 37 [0] 38 [0] 39 pcpu-alloc: [0] 40 [0] 41 [0] 42 [0] 43 [0] 44 [0] 45 [0] 46 [0] 47 pcpu-alloc: [0] 48 [0] 49 [0] 50 [0] 51 [0] 52 [0] 53 [0] 54 [0] 55 pcpu-alloc: [0] 56 [0] 57 [0] 58 [0] 59 [0] 60 [0] 61 [0] 62 [0] 63 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1034240 Kernel command line: root=/dev/disk/by-path/ccw-0.0.0100-part1 TERM=dumb BOOT_IMAGE=0 PID hash table entries: 4096 (order: 3, 32768 bytes) Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Memory: 4105820k/4194304k available (4398k kernel code, 0k reserved, 2099k data, 228k init) Write protected kernel read-only data: 0x10 - 0x5f Hierarchical RCU implementation. console [ttyS0] enabled allocated 41943040 bytes of page_cgroup please try 'cgroup_disable=memory' option if you
Re: hipersockets don't come up after HW upgrade
Roger, the minimum SLES11 SP1 kernel level should be 2.6.32.29-0.3.1. If you still have problems with a kernel level greater or equal to this one, something else is wrong. Which qeth-related messages show up in dmesg? What does "lsqeth" return? Regards, Ursula Braun, IBM Germany On Mon, 2011-11-07 at 16:04 +0100, Roger Evans wrote: > Thank you Ursula > > I don't seem to have the permissions to read those bugzilla entries, or > maybe I'm looking in the wrong Novell Bugzilla. > > Upgrading from sp3 to sp4 solved the problem for SLES10. > > I upgraded my SLES11sp1 with all the upgrades SuSE provides, but still > get the following msg: > -- > DPRODDB2:~ # ifup hsi0 > hsi0 name: Hipersocket (0.0.7000) > RTNETLINK answers: Unknown error 18446744073709486085 > Cannot enable interface hsi0. > interface hsi0 is not up > - > > I will go through the steps in the hipersocket configuration > instructions again. Maybe it's not enough to define it in YAST.. > -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Thank you Ursula I don't seem to have the permissions to read those bugzilla entries, or maybe I'm looking in the wrong Novell Bugzilla. Upgrading from sp3 to sp4 solved the problem for SLES10. I upgraded my SLES11sp1 with all the upgrades SuSE provides, but still get the following msg: -- DPRODDB2:~ # ifup hsi0 hsi0 name: Hipersocket (0.0.7000) RTNETLINK answers: Unknown error 18446744073709486085 Cannot enable interface hsi0. interface hsi0 is not up - I will go through the steps in the hipersocket configuration instructions again. Maybe it's not enough to define it in YAST.. Regards/Med vennlig hilsen Roger Evans Autodata Norge A/S On Mon, 2011-11-07 at 10:06 +0100, Ursula Braun wrote: > On Fri, 2011-11-04 at 15:18 +0200, Roger Evans wrote: > > Hi Sue > > > > Didn't seem to help. When booting with SLES10v2 I see the following > > when watching the boot from VM: > > - > > eth: IPv6 not supported on hsi0 > > qeth: Broadcast enabled > > qeth: Using SW checksumming on hsi0. > > qeth: Outbound TSO not supported on hsi0 > > operand exception: 0015 ¬Æ1| > > CPU: 0 Not tainted > > Process hwup-qeth (pid: 709, task: 0f400048, ksp: > > 0eee3960) > > Krnl PSW : 070400018000 1098cefa (do_QDIO+0x452/0x2a9c > > ¬qdio|) > > Krnl GPRS: 0001 00010006 8000 > > 8000 > > 00010006 000f > > 0e931000 0e4cf000 0e931000 > > 1097f000 10994960 0eee3ba8 0eee3aa8 > > Krnl Code: b2 22 00 30 88 30 00 1c 12 33 a7 84 00 0c bf 4f 92 50 a7 84 > > Call Trace: > > (¬<10b03a68>| qeth_dbf_setup+0x0/0xfffe7ad0 ¬qeth|) > > ¬<10adeafc>| __qeth_set_online+0x2780/0x2de4 ¬qeth| > > ¬<1081b544>| ccwgroup_online_store+0x10c/0x1fc ¬ccwgroup| > > ¬<002c43a0>| sysfs_write_file+0x120/0x190 > > ¬<002250f8>| sys_write+0x188/0x38c > > ¬<00115d10>| sysc_noemu+0x10/0x16 > > ¬<021c8738>| 0x21c8738 > > ..done > > Loading required kernel modules > > ¬1A..done<6>device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > > dm-devel > > ... > > -- > > > > I get this regardless of whether QIOASSIST is ON or OFF. > > > > Regards/ > > Med vennlig hilsen > > > > > > Roger Evans > > > Roger, > > the HiperSockets issue after HW upgrade requires a Linux upgrade: > - see Novell bugzilla 659101 for SLES11 SP1 > - see Novell bugzilla 662984 for SLES10 SP4 > - RHEL 5.7 > - RHEL 6.1 > > Description: qdio: use proper QEBSM operand for SIGA-R and SIGA-S > Symptom: Operand exception leading to kernel panic. > Problem: Wrong SIGA operand on QEBSM enabled qdio devices. > Solution:Use proper SIGA operands in QEBSM mode. > > Switching QIOASSIST OFF for HiperSockets Devices should circumvent the > problem. > > Regards, Ursula Braun, IBM Germany > > > -- > 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 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
On Fri, 2011-11-04 at 15:18 +0200, Roger Evans wrote: > Hi Sue > > Didn't seem to help. When booting with SLES10v2 I see the following > when watching the boot from VM: > - > eth: IPv6 not supported on hsi0 > qeth: Broadcast enabled > qeth: Using SW checksumming on hsi0. > qeth: Outbound TSO not supported on hsi0 > operand exception: 0015 ¬Æ1| > CPU: 0 Not tainted > Process hwup-qeth (pid: 709, task: 0f400048, ksp: > 0eee3960) > Krnl PSW : 070400018000 1098cefa (do_QDIO+0x452/0x2a9c > ¬qdio|) > Krnl GPRS: 0001 00010006 8000 > 8000 > 00010006 000f > 0e931000 0e4cf000 0e931000 > 1097f000 10994960 0eee3ba8 0eee3aa8 > Krnl Code: b2 22 00 30 88 30 00 1c 12 33 a7 84 00 0c bf 4f 92 50 a7 84 > Call Trace: > (¬<10b03a68>| qeth_dbf_setup+0x0/0xfffe7ad0 ¬qeth|) > ¬<10adeafc>| __qeth_set_online+0x2780/0x2de4 ¬qeth| > ¬<1081b544>| ccwgroup_online_store+0x10c/0x1fc ¬ccwgroup| > ¬<002c43a0>| sysfs_write_file+0x120/0x190 > ¬<002250f8>| sys_write+0x188/0x38c > ¬<00115d10>| sysc_noemu+0x10/0x16 > ¬<021c8738>| 0x21c8738 > ..done > Loading required kernel modules > ¬1A..done<6>device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > dm-devel > ... > -- > > I get this regardless of whether QIOASSIST is ON or OFF. > > Regards/ > Med vennlig hilsen > > > Roger Evans > Roger, the HiperSockets issue after HW upgrade requires a Linux upgrade: - see Novell bugzilla 659101 for SLES11 SP1 - see Novell bugzilla 662984 for SLES10 SP4 - RHEL 5.7 - RHEL 6.1 Description: qdio: use proper QEBSM operand for SIGA-R and SIGA-S Symptom: Operand exception leading to kernel panic. Problem: Wrong SIGA operand on QEBSM enabled qdio devices. Solution:Use proper SIGA operands in QEBSM mode. Switching QIOASSIST OFF for HiperSockets Devices should circumvent the problem. Regards, Ursula Braun, IBM Germany -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Display the kernel storage at 10b03a60.8 - in there is the instruction giving the exception. The b2220030 is the IPM used to retrieve the condition code from the previous instruction so it can be placed in a C variable. On 11/4/11 9:18 AM, "Roger Evans" wrote: > Hi Sue > > Didn't seem to help. When booting with SLES10v2 I see the following > when watching the boot from VM: > -- > -- > - > eth: IPv6 not supported on hsi0 > qeth: Broadcast enabled > qeth: Using SW checksumming on hsi0. > qeth: Outbound TSO not supported on hsi0 > operand exception: 0015 ¬Æ1| > CPU: 0 Not tainted > Process hwup-qeth (pid: 709, task: 0f400048, ksp: > 0eee3960) > Krnl PSW : 070400018000 1098cefa (do_QDIO+0x452/0x2a9c > ¬qdio|) > Krnl GPRS: 0001 00010006 8000 > 8000 > 00010006 000f > 0e931000 0e4cf000 0e931000 > 1097f000 10994960 0eee3ba8 0eee3aa8 > Krnl Code: b2 22 00 30 88 30 00 1c 12 33 a7 84 00 0c bf 4f 92 50 a7 84 > Call Trace: > (¬<10b03a68>| qeth_dbf_setup+0x0/0xfffe7ad0 ¬qeth|) > ¬<10adeafc>| __qeth_set_online+0x2780/0x2de4 ¬qeth| > ¬<1081b544>| ccwgroup_online_store+0x10c/0x1fc ¬ccwgroup| > ¬<002c43a0>| sysfs_write_file+0x120/0x190 > ¬<002250f8>| sys_write+0x188/0x38c > ¬<00115d10>| sysc_noemu+0x10/0x16 > ¬<021c8738>| 0x21c8738 > ..done > Loading required kernel modules > ¬1A..done<6>device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > dm-devel -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Hi Sue Didn't seem to help. When booting with SLES10v2 I see the following when watching the boot from VM: - eth: IPv6 not supported on hsi0 qeth: Broadcast enabled qeth: Using SW checksumming on hsi0. qeth: Outbound TSO not supported on hsi0 operand exception: 0015 ¬Æ1| CPU: 0 Not tainted Process hwup-qeth (pid: 709, task: 0f400048, ksp: 0eee3960) Krnl PSW : 070400018000 1098cefa (do_QDIO+0x452/0x2a9c ¬qdio|) Krnl GPRS: 0001 00010006 8000 8000 00010006 000f 0e931000 0e4cf000 0e931000 1097f000 10994960 0eee3ba8 0eee3aa8 Krnl Code: b2 22 00 30 88 30 00 1c 12 33 a7 84 00 0c bf 4f 92 50 a7 84 Call Trace: (¬<10b03a68>| qeth_dbf_setup+0x0/0xfffe7ad0 ¬qeth|) ¬<10adeafc>| __qeth_set_online+0x2780/0x2de4 ¬qeth| ¬<1081b544>| ccwgroup_online_store+0x10c/0x1fc ¬ccwgroup| ¬<002c43a0>| sysfs_write_file+0x120/0x190 ¬<002250f8>| sys_write+0x188/0x38c ¬<00115d10>| sysc_noemu+0x10/0x16 ¬<021c8738>| 0x21c8738 ..done Loading required kernel modules ¬1A..done<6>device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel ... -- I get this regardless of whether QIOASSIST is ON or OFF. Regards/ Med vennlig hilsen Roger Evans On Fri, 2011-11-04 at 08:07 -0400, Susan M. Farrell (620-3538) wrote: > Can you try turning off QIOASSIST for the guest and see > if that makes a difference? > > Regards, > Sue Farrell > > -- > 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 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
Can you try turning off QIOASSIST for the guest and see if that makes a difference? Regards, Sue Farrell -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
> What version of z/VM is this? z/VM Version 5 Release 4.0, Service Level 1101 (64-bit), > Do you have all the Linux related maintenance installed for it? Hard to tell. Is there one place we can go to find out what is needed? We have installed all the APARS that IBM told us were necessary to run VM on z114. Roger Evans Autodata Norge A/S Best Regards/Med vennlig hilsen Roger Evans Autodata Norge A/S On Tue, 2011-11-01 at 10:41 -0600, Mark Post wrote: > >>> On 11/1/2011 at 08:12 AM, Roger Evans wrote: > > SuSE 10.2 > > uname returns: kernel 2.6.16.60-0.21-default > > That's the SLES10 SP2 GA kernel, which is 2.5 years old. I think it might be > time to apply some maintenance. :( > > > I'm also trying to configure hsi0 with YAST on SuSE 11sp1 > > When I try to bring the interface up with ifup, I get: > > > > > > -- > > #ifup hsi0 > > hsi0 name: Hipersocket (0.0.7000) > > RTNETLINK answers: Unknown error 18446744073709486085 > > Cannot enable interface hsi0. > > > > -- > > What version of z/VM is this? Do you have all the Linux related maintenance > installed for it? > > > 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 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
>>> On 11/1/2011 at 08:12 AM, Roger Evans wrote: > SuSE 10.2 > uname returns: kernel 2.6.16.60-0.21-default That's the SLES10 SP2 GA kernel, which is 2.5 years old. I think it might be time to apply some maintenance. :( > I'm also trying to configure hsi0 with YAST on SuSE 11sp1 > When I try to bring the interface up with ifup, I get: > > > -- > #ifup hsi0 > hsi0 name: Hipersocket (0.0.7000) > RTNETLINK answers: Unknown error 18446744073709486085 > Cannot enable interface hsi0. > > -- What version of z/VM is this? Do you have all the Linux related maintenance installed for it? 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
SuSE 10.2 uname returns: kernel 2.6.16.60-0.21-default I'm also trying to configure hsi0 with YAST on SuSE 11sp1 When I try to bring the interface up with ifup, I get: -- #ifup hsi0 hsi0 name: Hipersocket (0.0.7000) RTNETLINK answers: Unknown error 18446744073709486085 Cannot enable interface hsi0. -- Med vennlig hilsen/regards Roger Evans On Mon, 2011-10-31 at 10:03 -0600, Mark Post wrote: > >>> On 10/31/2011 at 06:00 AM, Roger Evans wrote: > > Good morning, Mailing list > > We upgraded from a z9 to a z114 during the weekend, Most things seem > > to be working fine, but none of my linux hipersocket interfaces come > > up. > > > -snip- > > None of our VM or linux definitions have changed. > > > > The console on VSE shows the hipersocket as up. > > > > Any ideas? > > What distribution? What version and maintenance level? There was a bug in > udev that required both a kernel update and udev update to correct. > > > 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 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: hipersockets don't come up after HW upgrade
>>> On 10/31/2011 at 06:00 AM, Roger Evans wrote: > Good morning, Mailing list > We upgraded from a z9 to a z114 during the weekend, Most things seem > to be working fine, but none of my linux hipersocket interfaces come > up. > -snip- > None of our VM or linux definitions have changed. > > The console on VSE shows the hipersocket as up. > > Any ideas? What distribution? What version and maintenance level? There was a bug in udev that required both a kernel update and udev update to correct. 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
