http://bugzilla.novell.com/show_bug.cgi?id=527312 User mmarek@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=527312#c6 Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #6 from Michal Marek <mmarek@novell.com> 2009-08-13 01:07:51 MDT --- (In reply to comment #5)
Conspiracy theory 1: is it possible this happens in case the running kernel is different from the installed kernel (i.e., when as part of the same zypper dup run we previously updated the kernel)?
Running kernel does not matter, the only uname call in the script is when you run it with --add-kernel without an argument (maybe I should remove this).
Conspiracy theory 2: Or when there are several kernels installed?
Also should not matter and during each kernel update there are two kernels at some point.
Conspiracy theory 3: Or when I have a symlink within /lib/modules (which I _think_ was not the case here, but...)
Some havoc in /lib/modules might be the cause here, yes, but if you look at the add_kmp() function, it only proceeds with given kernel release if there exists /lib/modules/$krel and /boot/System.map-$krel. My private theory is some scripting error that overwrites the $krel variable, but then it should fail more deterministically. IOW I'm clueless here :-). Should you hit it once more, please run bash -x /usr/lib/module-init-tools/weak-modules2 --add-kmp $kmp where $kmp is the name-version-release of the affected kmp. I'll also ask on opensuse-factory if anyone has seen it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.