http://bugzilla.novell.com/show_bug.cgi?id=568120
http://bugzilla.novell.com/show_bug.cgi?id=568120#c28
--- Comment #28 from Angelika Schulz 2010-01-19 10:52:07 UTC ---
Hi there,
I installed the following packages:
kernel-xen + kernel-xen-base: booted fine, no problems
kernel-pae + kernel-pae-baes: booted fine, no problems
kernel-default + kernel-default-base: booted fine, no problems
No errors had been reported, despite that one (but for each version):
Could not load /lib/modules/kernel-<version>/systemtap/preloadtrace.ko
I guess that's intended?
The machine I installed yesterday had "kernel-desktop-2.6.31.5-0.1.1.i586"
installed fine and was running fine. Today a user logged in, started
applications (KDE4 + Kontact) and the machine got an oops ... so I had to
reboot the system. Having learned from the problem I started top on that
machine since it was quite slow, even for a nearly empty KDE4 session .. I
could see the preload_trace process using 99 percent of the CPU.
That machine only has 512MB RAM and started swapping right after Kontact had
been started - which _seemed_ to have caused the kernel oops together with the
frozen system. Shortly after booting the machine I used my chance and installed
kernel-default, which solved the problem completely - the machine is usable,
even with the 2.6.31.8 kernel.
I would like to know how opensuse determines which kernel flavor is needed,
since I had a big desktop of nearly the same age, 1GB RAM and it installed the
default kernel. But on the smaller desktop it installed the desktop flavor ...
For me the solution will be to get rid of the installed desktop kernel and
replace it by the default kernel. But that is the tricky part during an
automated installation.
Bye and thanks for your help,
Angie.
--
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.