[Bug 1539624] Re: hwup does not enable qeth when qeth driver is in the kernel (not a module)

[Dimitri John Ledkov]

In release pocket since 7th of February.

https://launchpad.net/ubuntu/+source/sysconfig/0.0.12

** Changed in: sysconfig (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1539624

Title:
  hwup does not enable qeth when qeth driver is in the kernel (not a
  module)

Status in sysconfig package in Ubuntu:
  Fix Released
Status in sysconfig package in Debian:
  Fix Released

Bug description:
  == Comment: #0 - EVGENY CHERKASHIN <Eugene.Crosser at ru.ibm.com> - 2016-01-29 06:22:37 ==
  When you boot a kernel that has qeth drivers (core, l2 and l3) compiled into the kernel as opposed to as modules, network interfaces fail to come up. E.g if you have this configuration:

  root at r35lp54:~# cat /etc/sysconfig/hardware/config-ccw-0.0.f100 
  CCWGROUP_CHANS=(0.0.f100 0.0.f101 0.0.f102)
  QETH_PORTNAME=OSAPORT
  QETH_PORTNO=0
  QETH_OPTIONS=()
  INTERFACE_NAME=eth1

  and run `hwup` command, you get this error message:

  root at r35lp54:~# hwup ccw 0.0.f100
  no kernel module for qeth devices available!

  Apparently `hwup-ccw-group` unconditionally runs `modprobe`; it should
  skip this step if the driver is already in the kernel.

  == Comment: #1 - Hendrik Brueckner <brueckner at de.ibm.com> - 2016-01-29 06:37:12 ==
  (In reply to comment #0)
  > When you boot a kernel that has qeth drivers (core, l2 and l3) compiled into
  > the kernel as opposed to as modules, network interfaces fail to come up. E.g
  > if you have this configuration:
  > 
  > root at r35lp54:~# cat /etc/sysconfig/hardware/config-ccw-0.0.f100 
  > CCWGROUP_CHANS=(0.0.f100 0.0.f101 0.0.f102)
  > QETH_PORTNAME=OSAPORT
  > QETH_PORTNO=0
  > QETH_OPTIONS=()
  > INTERFACE_NAME=eth1
  > 
  > and run `hwup` command, you get this error message:
  > 
  > root at r35lp54:~# hwup ccw 0.0.f100
  > no kernel module for qeth devices available!
  > 
  > Apparently `hwup-ccw-group` unconditionally runs `modprobe`; it should skip
  > this step if the driver is already in the kernel.

  Excerpt from hwup-ccw-group:
  --------------------
  elif [ "$NAME" == qeth ]; then
    modprobe qeth 2> /dev/null || :

    if [ -d $SYSFS/module/qeth ]; then
      DRIVER=qeth
    else
      error "no kernel module for qeth devices available!"
    fi
  fi
  -------------------

  Loading the module unconditionally is fine.  To correct the problem,
  the check for $SYSFS/module/qeth  needs to be updated, for example:

  /sys/bus/ccw/drivers/qeth
  /sys/devices/qeth

  == Comment: #2 - Hendrik Brueckner <brueckner at de.ibm.com> - 2016-01-29 06:53:03 ==
  A Debian bug report against the sysconfig-hardware package has been submitted. I will update the bugzilla when I have the debian bug number available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysconfig/+bug/1539624/+subscriptions