Right, we also understand that our generic kernel will (a) use more than available 32MB of ram (b) doesn't have the scsi/zfcp modules built in. Even if we built-in scsi/zfcp modules, we are guessing it will still be no good. Hence we really must get a zfcpdump.image building. At the moment we are debating to build it as a standalone source and binary package, based on the ubuntu linux-source package, which is only rebuild infrequently (e.g. once per ga) and not rebuild on avery kernel update, as any kernel base should be sufficient for zfcpdump. Does zfcdump.image must match the crashed kernel image? On Ubuntu one can have multiple kernels installed, and it's not possible to know which one is currently active one - or rather it's not possible to make sure that zfcdump.image on disk is a matching kernel as the currently running (crashed) standard kernel.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1565841 Title: Provide zfcpdump-infrastructure with Ubuntu 16.04 Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in linux source package in Xenial: New Status in s390-tools source package in Xenial: New Status in linux source package in y-series: New Status in s390-tools source package in y-series: New Bug description: == Comment: #0 - Heinz-Werner Seeck - 2016-04-04 10:59:10 == Please provide the zfcpdump infrastructure to Ubuntu 16.04 , to enhance RAS capabilities and better Service enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
