[opensuse-buildservice] Building KMP packages
Hi, I'm experimenting with kmp packages, the thing is that if the version don't match exactly the version of the kernel I can't load them... Current kernel installs modules in /lib/modules/2.6.32.45-0.3-pae, but my OBS generated kmp puts them in /lib/modules/2.6.32.45-1-pae/updates. In that situation, modprobe fails with "ERROR: modinfo: could not find module <name>". I tought kmp could handle minor version changes in kernel, although in this case I've built the kmp with that exact same target kernel, OBS is the one changing the release numbers.. Any advices? -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
On 9/14/2011 at 09:04 AM, in message <CAEaLa5EiKCAOEFeGzbRUxw_x5Y5dzK5bCk2bqK7u2TJnXX_8tg@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: Hi, I'm experimenting with kmp packages, the thing is that if the version don't match exactly the version of the kernel I can't load them...
Current kernel installs modules in /lib/modules/2.6.32.45-0.3-pae, but my OBS generated kmp puts them in /lib/modules/2.6.32.45-1-pae/updates. In that situation, modprobe fails with "ERROR: modinfo: could not find module <name>".
I tought kmp could handle minor version changes in kernel, although in this case I've built the kmp with that exact same target kernel, OBS is the one changing the release numbers..
I assume you're building against SLES 11 SP1...? KMP should be able to handle this change as long as the symsets required by your KMP are satisfied by the running kernel. When the KMP is installed, you should get a /lib/modules/2.6.32.45-0.3-pae/updates/weak-updates/<driver-name> link that points to /lib/modules/2.6.32.45-1-pae/updates/<driver-name>. Do you get this link? Regards, Ann
Any advices?
-- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2011/9/14 Ann Davis <andavis@suse.com>:
Hi,
On 9/14/2011 at 09:04 AM, in message <CAEaLa5EiKCAOEFeGzbRUxw_x5Y5dzK5bCk2bqK7u2TJnXX_8tg@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: Hi, I'm experimenting with kmp packages, the thing is that if the version don't match exactly the version of the kernel I can't load them...
Current kernel installs modules in /lib/modules/2.6.32.45-0.3-pae, but my OBS generated kmp puts them in /lib/modules/2.6.32.45-1-pae/updates. In that situation, modprobe fails with "ERROR: modinfo: could not find module <name>".
I tought kmp could handle minor version changes in kernel, although in this case I've built the kmp with that exact same target kernel, OBS is the one changing the release numbers..
I assume you're building against SLES 11 SP1...? KMP should be able to handle this change as long as the symsets required by your KMP are satisfied by the running kernel. When the KMP is installed, you should get a /lib/modules/2.6.32.45-0.3-pae/updates/weak-updates/<driver-name> link that points to /lib/modules/2.6.32.45-1-pae/updates/<driver-name>. Do you get this link?
Regards,
Ann
Yes, I'm recompiling ip_vs included on HAE with latest kernel update available... glb1:~ # rpm -ql cluster-network-kmp-pae /lib/modules/2.6.32.45-1-pae /lib/modules/2.6.32.45-1-pae/updates /lib/modules/2.6.32.45-1-pae/updates/ipvs /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_dh.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_ftp.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lblc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lblcr.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_nq.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_rr.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_sed.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_sh.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_wlc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_wrr.ko /lib/modules/2.6.32.45-1-pae/updates/netfilter /lib/modules/2.6.32.45-1-pae/updates/netfilter/ipt_CLUSTERIP.ko glb1:~ # find /lib/modules/$(uname -r) -iname "*updates*" /lib/modules/2.6.32.45-0.3-pae/weak-updates /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates There are no links for ip_vs.ko after installing kmp package... Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
On 9/14/2011 at 02:25 PM, in message <CAEaLa5EAGuviQS8DokqXZHQ-hBkw4iZhD51RtFu13apW9ynmxQ@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: 2011/9/14 Ann Davis <andavis@suse.com>: Hi,
On 9/14/2011 at 09:04 AM, in message <CAEaLa5EiKCAOEFeGzbRUxw_x5Y5dzK5bCk2bqK7u2TJnXX_8tg@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: Hi, I'm experimenting with kmp packages, the thing is that if the version don't match exactly the version of the kernel I can't load them...
Current kernel installs modules in /lib/modules/2.6.32.45-0.3-pae, but my OBS generated kmp puts them in /lib/modules/2.6.32.45-1-pae/updates. In that situation, modprobe fails with "ERROR: modinfo: could not find module <name>".
I tought kmp could handle minor version changes in kernel, although in this case I've built the kmp with that exact same target kernel, OBS is the one changing the release numbers..
I assume you're building against SLES 11 SP1...? KMP should be able to handle this change as long as the symsets required by your KMP are satisfied by the running kernel. When the KMP is installed, you should get a /lib/modules/2.6.32.45-0.3-pae/updates/weak-updates/<driver-name> link that points to /lib/modules/2.6.32.45-1-pae/updates/<driver-name>. Do you get this link?
Regards,
Ann
Yes, I'm recompiling ip_vs included on HAE with latest kernel update available...
glb1:~ # rpm -ql cluster-network-kmp-pae /lib/modules/2.6.32.45-1-pae /lib/modules/2.6.32.45-1-pae/updates /lib/modules/2.6.32.45-1-pae/updates/ipvs /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_dh.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_ftp.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lblc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lblcr.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_nq.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_rr.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_sed.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_sh.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_wlc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_wrr.ko /lib/modules/2.6.32.45-1-pae/updates/netfilter /lib/modules/2.6.32.45-1-pae/updates/netfilter/ipt_CLUSTERIP.ko
glb1:~ # find /lib/modules/$(uname -r) -iname "*updates*" /lib/modules/2.6.32.45-0.3-pae/weak-updates /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates
There are no links for ip_vs.ko after installing kmp package.
The above looks fine, but it doesn't indicate whether there are any files or links in /lib/modules/$(uname -r)/weak-updates/updates/. What is the output of "find /lib/modules/$(uname -r)/weak-updates/updates/? There should be links here. Note that the links are created by the kmp postinstall, so they won't appear in "rpm -ql cluster-network-kmp-pae". If there are no links in /lib/modules/$(uname -r)/weak-updates/updates/, then what is the output of "rpm -q --scripts cluster-network-kmp-pae"? This should show the postinstall script that makes the links. Thanks, Ann
Regards,
-- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2011/9/14 Ann Davis <andavis@suse.com>:
Hi,
On 9/14/2011 at 02:25 PM, in message <CAEaLa5EAGuviQS8DokqXZHQ-hBkw4iZhD51RtFu13apW9ynmxQ@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: 2011/9/14 Ann Davis <andavis@suse.com>: Hi,
On 9/14/2011 at 09:04 AM, in message <CAEaLa5EiKCAOEFeGzbRUxw_x5Y5dzK5bCk2bqK7u2TJnXX_8tg@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: Hi, I'm experimenting with kmp packages, the thing is that if the version don't match exactly the version of the kernel I can't load them...
Current kernel installs modules in /lib/modules/2.6.32.45-0.3-pae, but my OBS generated kmp puts them in /lib/modules/2.6.32.45-1-pae/updates. In that situation, modprobe fails with "ERROR: modinfo: could not find module <name>".
I tought kmp could handle minor version changes in kernel, although in this case I've built the kmp with that exact same target kernel, OBS is the one changing the release numbers..
I assume you're building against SLES 11 SP1...? KMP should be able to handle this change as long as the symsets required by your KMP are satisfied by the running kernel. When the KMP is installed, you should get a /lib/modules/2.6.32.45-0.3-pae/updates/weak-updates/<driver-name> link that points to /lib/modules/2.6.32.45-1-pae/updates/<driver-name>. Do you get this link?
Regards,
Ann
Yes, I'm recompiling ip_vs included on HAE with latest kernel update available...
glb1:~ # rpm -ql cluster-network-kmp-pae /lib/modules/2.6.32.45-1-pae /lib/modules/2.6.32.45-1-pae/updates /lib/modules/2.6.32.45-1-pae/updates/ipvs /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_dh.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_ftp.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lblc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lblcr.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_nq.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_rr.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_sed.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_sh.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_wlc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_wrr.ko /lib/modules/2.6.32.45-1-pae/updates/netfilter /lib/modules/2.6.32.45-1-pae/updates/netfilter/ipt_CLUSTERIP.ko
glb1:~ # find /lib/modules/$(uname -r) -iname "*updates*" /lib/modules/2.6.32.45-0.3-pae/weak-updates /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates
There are no links for ip_vs.ko after installing kmp package.
The above looks fine, but it doesn't indicate whether there are any files or links in /lib/modules/$(uname -r)/weak-updates/updates/. What is the output of "find /lib/modules/$(uname -r)/weak-updates/updates/? There should be links here.
Note that the links are created by the kmp postinstall, so they won't appear in "rpm -ql cluster-network-kmp-pae".
If there are no links in /lib/modules/$(uname -r)/weak-updates/updates/, then what is the output of "rpm -q --scripts cluster-network-kmp-pae"? This should show the postinstall script that makes the links.
Thanks,
Ann
Regards,
Didn't want to clutter your script with the output :) glb1:~ # find /lib/modules/$(uname -r)/weak-updates -ls 56528 0 drwxr-xr-x 4 root root 96 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates 56531 0 drwxr-xr-x 3 root root 80 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/extra 56532 0 drwxr-xr-x 3 root root 104 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/extra/hp-nx_nic 56535 0 lrwxrwxrwx 1 root root 58 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/extra/hp-nx_nic/nx_xport.ko -> /lib/modules/2.6.32.24-0.2-pae/extra/hp-nx_nic/nx_xport.ko 56533 0 drwxr-xr-x 2 root root 80 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/extra/hp-nx_nic/driver 56534 0 lrwxrwxrwx 1 root root 63 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/extra/hp-nx_nic/driver/nx_nic.ko -> /lib/modules/2.6.32.24-0.2-pae/extra/hp-nx_nic/driver/nx_nic.ko 56529 0 drwxr-xr-x 5 root root 216 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates 56543 0 drwxr-xr-x 2 root root 80 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/hp-be2net 56544 0 lrwxrwxrwx 1 root root 58 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/hp-be2net/be2net.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/hp-be2net/be2net.ko 56542 0 lrwxrwxrwx 1 root root 48 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/e1000e.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/e1000e.ko 56536 0 drwxr-xr-x 3 root root 72 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/drivers 56537 0 drwxr-xr-x 3 root root 72 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/drivers/net 56538 0 drwxr-xr-x 2 root root 112 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/drivers/net/mlx4 56539 0 lrwxrwxrwx 1 root root 68 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/drivers/net/mlx4/mlx4_core.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/drivers/net/mlx4/mlx4_core.ko 56540 0 lrwxrwxrwx 1 root root 66 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/drivers/net/mlx4/mlx4_en.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/drivers/net/mlx4/mlx4_en.ko 56530 0 lrwxrwxrwx 1 root root 45 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/tg3.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/tg3.ko 56545 0 drwxr-xr-x 2 root root 80 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/hp-be2iscsi 56546 0 lrwxrwxrwx 1 root root 62 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/hp-be2iscsi/be2iscsi.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/hp-be2iscsi/be2iscsi.ko 56541 0 lrwxrwxrwx 1 root root 47 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/e1000.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/e1000.ko glb1:~ # rpm -q --scripts cluster-network-kmp-pae postinstall scriptlet (using /bin/sh): nvr=cluster-network-kmp-pae-1.4_2.6.32.45_1-4.4 wm2=/usr/lib/module-init-tools/weak-modules2 if [ -x $wm2 ]; then /bin/bash -${-/e/} $wm2 --add-kmp $nvr fi preuninstall scriptlet (using /bin/sh): nvr=cluster-network-kmp-pae-1.4_2.6.32.45_1-4.4 rpm -ql $nvr | sed -n '/\.ko$/p' > /var/run/rpm-$nvr-modules postuninstall scriptlet (using /bin/sh): nvr=cluster-network-kmp-pae-1.4_2.6.32.45_1-4.4 modules=( $(cat /var/run/rpm-$nvr-modules) ) rm -f /var/run/rpm-$nvr-modules if [ ${#modules[*]} = 0 ]; then echo "WARNING: $nvr does not contain any kernel modules" >&2 exit 0 fi wm2=/usr/lib/module-init-tools/weak-modules2 if [ -x $wm2 ]; then printf '%s\n' "${modules[@]}" | /bin/bash -${-/e/} $wm2 --remove-kmp $nvr fi Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2011/9/14 Ciro Iriarte <cyruspy@gmail.com>:
Didn't want to clutter your script with the output :)
Sorry, multitasking issues, should read "screen"... -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Ciro,
On 9/14/2011 at 03:35 PM, in message <CAEaLa5FWLBt+m-_c9N4kK6n-2L1+GJO9OxgxBz5Mb_rRwVFbMA@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: 2011/9/14 Ann Davis <andavis@suse.com>: Hi,
On 9/14/2011 at 02:25 PM, in message <CAEaLa5EAGuviQS8DokqXZHQ-hBkw4iZhD51RtFu13apW9ynmxQ@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: 2011/9/14 Ann Davis <andavis@suse.com>: Hi,
> On 9/14/2011 at 09:04 AM, in message <CAEaLa5EiKCAOEFeGzbRUxw_x5Y5dzK5bCk2bqK7u2TJnXX_8tg@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: Hi, I'm experimenting with kmp packages, the thing is that if the version don't match exactly the version of the kernel I can't load them...
Current kernel installs modules in /lib/modules/2.6.32.45-0.3-pae, but my OBS generated kmp puts them in /lib/modules/2.6.32.45-1-pae/updates. In that situation, modprobe fails with "ERROR: modinfo: could not find module <name>".
I tought kmp could handle minor version changes in kernel, although in this case I've built the kmp with that exact same target kernel, OBS is the one changing the release numbers..
I assume you're building against SLES 11 SP1...? KMP should be able to handle this change as long as the symsets required by your KMP are satisfied by the running kernel. When the KMP is installed, you should get a /lib/modules/2.6.32.45-0.3-pae/updates/weak-updates/<driver-name> link that points to /lib/modules/2.6.32.45-1-pae/updates/<driver-name>. Do you get this link?
Regards,
Ann
Yes, I'm recompiling ip_vs included on HAE with latest kernel update available...
glb1:~ # rpm -ql cluster-network-kmp-pae /lib/modules/2.6.32.45-1-pae /lib/modules/2.6.32.45-1-pae/updates /lib/modules/2.6.32.45-1-pae/updates/ipvs /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_dh.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_ftp.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lblc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lblcr.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_lc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_nq.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_rr.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_sed.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_sh.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_wlc.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs_wrr.ko /lib/modules/2.6.32.45-1-pae/updates/netfilter /lib/modules/2.6.32.45-1-pae/updates/netfilter/ipt_CLUSTERIP.ko
glb1:~ # find /lib/modules/$(uname -r) -iname "*updates*" /lib/modules/2.6.32.45-0.3-pae/weak-updates /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates
There are no links for ip_vs.ko after installing kmp package.
The above looks fine, but it doesn't indicate whether there are any files or links in /lib/modules/$(uname -r)/weak-updates/updates/. What is the output of "find /lib/modules/$(uname -r)/weak-updates/updates/? There should be links here.
Note that the links are created by the kmp postinstall, so they won't appear in "rpm -ql cluster-network-kmp-pae".
If there are no links in /lib/modules/$(uname -r)/weak-updates/updates/, then what is the output of "rpm -q --scripts cluster-network-kmp-pae"? This should show the postinstall script that makes the links.
Thanks,
Ann
Regards,
Didn't want to clutter your script with the output :)
Thanks :), see my comments below...
glb1:~ # find /lib/modules/$(uname -r)/weak-updates -ls 56528 0 drwxr-xr-x 4 root root 96 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates 56531 0 drwxr-xr-x 3 root root 80 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/extra 56532 0 drwxr-xr-x 3 root root 104 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/extra/hp-nx_nic 56535 0 lrwxrwxrwx 1 root root 58 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/extra/hp-nx_nic/nx_xport.ko -> /lib/modules/2.6.32.24-0.2-pae/extra/hp-nx_nic/nx_xport.ko 56533 0 drwxr-xr-x 2 root root 80 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/extra/hp-nx_nic/driver 56534 0 lrwxrwxrwx 1 root root 63 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/extra/hp-nx_nic/driver/nx_nic.ko -> /lib/modules/2.6.32.24-0.2-pae/extra/hp-nx_nic/driver/nx_nic.ko 56529 0 drwxr-xr-x 5 root root 216 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates 56543 0 drwxr-xr-x 2 root root 80 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/hp-be2net 56544 0 lrwxrwxrwx 1 root root 58 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/hp-be2net/be2net.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/hp-be2net/be2net.ko 56542 0 lrwxrwxrwx 1 root root 48 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/e1000e.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/e1000e.ko 56536 0 drwxr-xr-x 3 root root 72 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/drivers 56537 0 drwxr-xr-x 3 root root 72 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/drivers/net 56538 0 drwxr-xr-x 2 root root 112 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/drivers/net/mlx4 56539 0 lrwxrwxrwx 1 root root 68 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/drivers/net/mlx4/mlx4_co re.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/drivers/net/mlx4/mlx4_core.ko 56540 0 lrwxrwxrwx 1 root root 66 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/drivers/net/mlx4/mlx4_en .ko -> /lib/modules/2.6.32.24-0.2-pae/updates/drivers/net/mlx4/mlx4_en.ko 56530 0 lrwxrwxrwx 1 root root 45 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/tg3.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/tg3.ko 56545 0 drwxr-xr-x 2 root root 80 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/hp-be2iscsi 56546 0 lrwxrwxrwx 1 root root 62 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/hp-be2iscsi/be2iscsi.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/hp-be2iscsi/be2iscsi.ko 56541 0 lrwxrwxrwx 1 root root 47 Sep 13 15:58 /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/e1000.ko -> /lib/modules/2.6.32.24-0.2-pae/updates/e1000.ko
glb1:~ # rpm -q --scripts cluster-network-kmp-pae postinstall scriptlet (using /bin/sh): nvr=cluster-network-kmp-pae-1.4_2.6.32.45_1-4.4 wm2=/usr/lib/module-init-tools/weak-modules2 if [ -x $wm2 ]; then /bin/bash -${-/e/} $wm2 --add-kmp $nvr fi preuninstall scriptlet (using /bin/sh): nvr=cluster-network-kmp-pae-1.4_2.6.32.45_1-4.4 rpm -ql $nvr | sed -n '/\.ko$/p' > /var/run/rpm-$nvr-modules postuninstall scriptlet (using /bin/sh): nvr=cluster-network-kmp-pae-1.4_2.6.32.45_1-4.4 modules=( $(cat /var/run/rpm-$nvr-modules) ) rm -f /var/run/rpm-$nvr-modules if [ ${#modules[*]} = 0 ]; then echo "WARNING: $nvr does not contain any kernel modules" >&2 exit 0 fi wm2=/usr/lib/module-init-tools/weak-modules2 if [ -x $wm2 ]; then printf '%s\n' "${modules[@]}" | /bin/bash -${-/e/} $wm2 --remove-kmp $nvr fi
The postinstall script is fine but the links didn't get made. So this means that the "/bin/bash -${-/e/} $wm2 --add-kmp $nvr" command in the postinstall scriptlet failed to make the links. This command just calls the "/usr/lib/module-init-tools/weak-modules2" script if you want to take a look at what it does. The most likely reason for the weak-modules2 script not to make links would be that the symsets required by your -kmp package are not provided by the running kernel. To see the symsets required by your kmp, run "rpm -q --requires cluster-network-kmp-pae". What is that output? Then compare it to the symsets provided by your running kernel as listed in /boot/symsets-$(uname -r).tar.gz. Regards, Ann
Regards,
-- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Ann, 2011/9/14 Ann Davis <andavis@suse.com>:
The postinstall script is fine but the links didn't get made. So this means that the "/bin/bash -${-/e/} $wm2 --add-kmp $nvr" command in the postinstall scriptlet failed to make the links. This command just calls the "/usr/lib/module-init-tools/weak-modules2" script if you want to take a look at what it does.
## weak-modules2 ## Execution: bash -x /usr/lib/module-init-tools/weak-modules2 --add-kmp cluster-network-kmp-pae-1.4_2.6.32.45_1-4.4 Output: http://pastebin.com/KGxYkML1
The most likely reason for the weak-modules2 script not to make links would be that the symsets required by your -kmp package are not provided by the running kernel. To see the symsets required by your kmp, run "rpm -q --requires cluster-network-kmp-pae". What is that output? Then compare it to the symsets provided by your running kernel as listed in /boot/symsets-$(uname -r).tar.gz.
"Requires" output: http://pastebin.com/rvhbsgE1 All 58 symbols match... glb1:~ # zcat /boot/symsets-$(uname -r).tar.gz|strings > symsets.txt glb1:~ # rpm -q --requires cluster-network-kmp-pae |grep kernel|cut -f 2 -d "="|wc -l 58 glb1:~ # for ID in $(rpm -q --requires cluster-network-kmp-pae |grep kernel|cut -f 2 -d "=");do grep $ID symsets.txt ;done|wc -l 58
Ann
Regards,
Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Ciro,
On 9/15/2011 at 09:25 AM, in message <CAEaLa5E5iG3vnWZ6LomEcGVMh_Ncq4FiZAHxUYQtwz-CgbJnrw@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: Ann,
2011/9/14 Ann Davis <andavis@suse.com>:
The postinstall script is fine but the links didn't get made. So this means
"/bin/bash -${-/e/} $wm2 --add-kmp $nvr" command in the postinstall
that the scriptlet failed to make the links. This command just calls the "/usr/lib/module-init-tools/weak-modules2" script if you want to take a look at what it does.
## weak-modules2 ##
Execution: bash -x /usr/lib/module-init-tools/weak-modules2 --add-kmp cluster-network-kmp-pae-1.4_2.6.32.45_1-4.4
Output: http://pastebin.com/KGxYkML1
Aha, I believe you have hit a known bug where the weak-modules2 script does not make the links if the /lib/modules/$version tree has kabi mismatches. (Actually, if you look at the output, weak-modules2 makes the links then removes them after it sees the mismatches due to the infiniband drivers). One of the bugs on this is bugzilla #707793 (I don't know if you have access...) but I remember that there's another bug with more info. I believe the core issue is with the HP PSP infiniband drivers that cause the mismatch but let me do a little research if I can find more info. Ann
The most likely reason for the weak-modules2 script not to make links would
be that the symsets required by your -kmp package are not provided by the running kernel. To see the symsets required by your kmp, run "rpm -q --requires cluster-network-kmp-pae". What is that output? Then compare it to the symsets provided by your running kernel as listed in
/boot/symsets-$(uname -r).tar.gz.
"Requires" output: http://pastebin.com/rvhbsgE1
All 58 symbols match...
glb1:~ # zcat /boot/symsets-$(uname -r).tar.gz|strings > symsets.txt glb1:~ # rpm -q --requires cluster-network-kmp-pae |grep kernel|cut -f 2 -d "="|wc -l 58 glb1:~ # for ID in $(rpm -q --requires cluster-network-kmp-pae |grep kernel|cut -f 2 -d "=");do grep $ID symsets.txt ;done|wc -l 58
Ann
Regards,
Regards,
-- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 9/15/2011 at 10:30 AM, in message <4E71D3B4020000D6000C7E1E@novprvoes0310.provo.novell.com>, "Ann Davis" <andavis@suse.com> wrote: Ciro,
On 9/15/2011 at 09:25 AM, in message <CAEaLa5E5iG3vnWZ6LomEcGVMh_Ncq4FiZAHxUYQtwz-CgbJnrw@mail.gmail.com>, Ciro Iriarte <cyruspy@gmail.com> wrote: Ann,
2011/9/14 Ann Davis <andavis@suse.com>:
The postinstall script is fine but the links didn't get made. So this means
"/bin/bash -${-/e/} $wm2 --add-kmp $nvr" command in the postinstall
that the scriptlet failed to make the links. This command just calls the "/usr/lib/module-init-tools/weak-modules2" script if you want to take a look at what it does.
## weak-modules2 ##
Execution: bash -x /usr/lib/module-init-tools/weak-modules2 --add-kmp cluster-network-kmp-pae-1.4_2.6.32.45_1-4.4
Output: http://pastebin.com/KGxYkML1
Aha, I believe you have hit a known bug where the weak-modules2 script does not make the links if the /lib/modules/$version tree has kabi mismatches. (Actually, if you look at the output, weak-modules2 makes the links then removes them after it sees the mismatches due to the infiniband drivers). One of the bugs on this is bugzilla #707793 (I don't know if you have access...) but I remember that there's another bug with more info. I believe the core issue is with the HP PSP infiniband drivers that cause the mismatch but let me do a little research if I can find more info.
The original bugzilla is #682078 and the problem is with the hp-mlnx-en-kmp rpm. I believe that the HP PSP installs this rpm even if your system doesn't have a mellanox card. So if you don't need hp-mlnx-en-kmp, you might want to remove it then install your kmp. I think that should take care of the problem... for this and future kmp installs. BTW, thanks for posting the detailed weak-modules2 output, that was the key for debugging. :) Ann
Ann
The most likely reason for the weak-modules2 script not to make links would
be that the symsets required by your -kmp package are not provided by the running kernel. To see the symsets required by your kmp, run "rpm -q --requires cluster-network-kmp-pae". What is that output? Then compare it to the symsets provided by your running kernel as listed in
/boot/symsets-$(uname -r).tar.gz.
"Requires" output: http://pastebin.com/rvhbsgE1
All 58 symbols match...
glb1:~ # zcat /boot/symsets-$(uname -r).tar.gz|strings > symsets.txt glb1:~ # rpm -q --requires cluster-network-kmp-pae |grep kernel|cut -f 2 -d "="|wc -l 58 glb1:~ # for ID in $(rpm -q --requires cluster-network-kmp-pae |grep kernel|cut -f 2 -d "=");do grep $ID symsets.txt ;done|wc -l 58
Ann
Regards,
Regards,
-- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Ann, 2011/9/15 Ann Davis <andavis@suse.com>:
Aha, I believe you have hit a known bug where the weak-modules2 script does not make the links if the /lib/modules/$version tree has kabi mismatches. (Actually, if you look at the output, weak-modules2 makes the links then removes them after it sees the mismatches due to the infiniband drivers). One of the bugs on this is bugzilla #707793 (I don't know if you have access...) but I remember that there's another bug with more info. I believe
Unluckily, I dont'..
the core issue is with the HP PSP infiniband drivers that cause the mismatch but let me do a little research if I can find more info.
The original bugzilla is #682078 and the problem is with the hp-mlnx-en-kmp rpm. I believe that the HP PSP installs this rpm even if your system doesn't have a mellanox card. So if you don't need hp-mlnx-en-kmp, you might want to remove it then install your kmp. I think that should take care of the problem... for this and future kmp installs.
The weird thing is, previously I didn't have this issue (original packaged rpm). Certainly, removing hp-mlnx-en-kmp-pae package allows link creation glb1:~ # find /lib/modules/ -name ip_vs.ko /lib/modules/2.6.32.45-1-pae/updates/ipvs/ip_vs.ko /lib/modules/2.6.32.45-0.3-pae/weak-updates/updates/ipvs/ip_vs.ko
BTW, thanks for posting the detailed weak-modules2 output, that was the key for debugging. :)
Thanks for taking a look at the issue :)
Ann
Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Ann Davis -
Ciro Iriarte