https://bugzilla.novell.com/show_bug.cgi?id=350896 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350896#c1 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com Status|NEW |NEEDINFO Info Provider| |roland.kletzing@materna.de --- Comment #1 from Jeff Mahoney 2008-01-02 15:53:37 MST --- There's probably an unterminated array somewhere that it's traversing and hasn't managed to hit a NULL where it expects one. Can you see if -git7 shows the same problem? If so, please provide the output of strace depmod -ae -F Systemp.map from the kernel build directory. It should at least help narrow down which module is causing it to go nuts. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350896 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350896#c3 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |mmarek@novell.com Status|NEEDINFO |NEW Info Provider|roland.kletzing@materna.de | --- Comment #3 from Jeff Mahoney 2008-01-02 18:26:05 MST --- Huh, that's interesting. I think that our kernel RPMs take advantage of some RPM magic here. Our raw configs (ie: not in /proc/config.gz) don't actually set CONFIG_DEBUG_INFO - it's set in the RPM, and then the debug sections are stripped off the binaries to make the -debuginfo package. This might even happen before make modules_install is run, but I'm not an RPM guru. Now, I agree there's a bug here, and I'm going to pass it on to our module-init-tools maintainer for review. The thing is that we publish a vanilla flavor for all our kernel RPMs. So, you'll have your kernel-default RPM, but there is also a kernel-vanilla. It is identical to the vanilla kernel with the exception that there are a few patches applied to get it to build in our environment. The section-conflict ones are because the compiler on ia64 complains when module parameter functions are static. powerpc-needs-uboot is only for powerpc, and gcc43 workaround will be a no-op if you're not using gcc 4.3. If you were, you would have run into build failure relating to time and an unresolvable __udivdi3 call. Here's the current list: patches.kernel.org/powerpc-needs-uboot patches.kernel.org/gcc43-workaround.diff patches.kernel.org/ia64-jprobe-return-section-conflict.diff patches.kernel.org/gameport-section-conflict.diff patches.kernel.org/psmouse-section-conflict.diff patches.kernel.org/ipmi-section-conflict.diff I understand that you may be wary about using it, but that's your call. For the time being, your only option may be to either strip and build your own debuginfo tree or to disable CONFIG_DEBUG_INFO. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.