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: 000000000f400048, ksp:
> > 000000000eee3960)
> > Krnl PSW : 0704000180000000 000000001098cefa (do_QDIO+0x452/0x2a9c
> > ¬qdio|)
> > Krnl GPRS: 0000000000000001 0000000000010006 0000000080000000
> > 0000000080000000
> > 0000000000010006 0000000000000000 0000000000000000 000000000000000f
> > 0000000000000000 000000000e931000 000000000e4cf000 000000000e931000
> > 000000001097f000 0000000010994960 000000000eee3ba8 000000000eee3aa8
> > Krnl Code: b2 22 00 30 88 30 00 1c 12 33 a7 84 00 0c bf 4f 92 50 a7 84
> > Call Trace:
> > (¬<0000000010b03a68>| qeth_dbf_setup+0x0/0xfffffffffffe7ad0 ¬qeth|)
> > ¬<0000000010adeafc>| __qeth_set_online+0x2780/0x2de4 ¬qeth|
> > ¬<000000001081b544>| ccwgroup_online_store+0x10c/0x1fc ¬ccwgroup|
> > ¬<00000000002c43a0>| sysfs_write_file+0x120/0x190
> > ¬<00000000002250f8>| sys_write+0x188/0x38c
> > ¬<0000000000115d10>| sysc_noemu+0x10/0x16
> > ¬<00000200001c8738>| 0x200001c8738
> > ..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/
