On Mon, 2012-06-18 at 10:15 +0100, Malcolm Beattie wrote: > Ursula Braun writes: > > correct, state HARDSETUP should be a temporary state during online > > setting for a qeth device only. If the device stays in state HARDSETUP > > something unexpected occurred. To understand the reason, the trace > > file /sys/kernel/debugfs/qeth_setup/hex_ascii should be checked by a > > qeth expert. It's a wrap around buffer; thus it needs to be saved > > immediately after the problem shows up. > > I can reproduce this easily on SLES11SP1 kernel 2.6.32.12-0.7-default > (not up to date on service at all). I'll send you a transcript.
Malcolm, looking through your transcript, I find the definition of the NIC (vmcp def nic 800 type qdio), but I do not see a vmcp couple command to bind the created NIC to a VSWITCH or GuestLAN. This would explain the failing STARTLAN command for this qeth device. Try to insert a vmcp couple command between "vmcp def nic..." and "znetconf -a ..." . Regards, Ursula Braun, IBM Germany ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] 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/
