Two hundred staprun error messages upon booting

English Install/Boot/Login
1

Hello:
Every boot, I see screenfuls of staprun error messages fly by, e.g from /var/log/boot.msg:

<notice -- Aug 31 23:39:53.511288000> service boot.startpreload startstaprun:send_a_relocation:336: ERROR: reloc name too long: .gnu.linkonce.r._ZN6AsicNII18ucode_class_caymanE23NITiling
ModeLookupTableE: No such file or directory
staprun:send_a_relocation:336: ERROR: reloc name too long: .gnu.linkonce.r._ZTV15WritebacksBlockIN11mmEngineUVD16WRITEBACKS_BLOCKEE: No such file or directory
.
.
.

...200 more messages...

Anybody else seeing anything like this? Can I just remove staprun?

My system details:

/etc/SuSE-release:
openSUSE 11.3 (x86_64)
VERSION = 11.3

KDE:
Version: 4.4.4-1.5

uname: 2.6.34-12-desktop #1 SMP PREEMPT x86_64

Thanks for any assistance.

2

Not really.
I’m thinking turn it off

sudo service chkconfig boot.startpreload off
3

This could be an indication of file system or disk corruption. From a bootable Linux disk like Parted Magic run fsck on the partition.

4

It’s always worth checking on disk health. In this case, though, both e2fsck and Gparted, from Puppy Linux, show everything is clean.

5

Hello,

I have the same problem here with this bunch of staprun messages. I just created a boot CD and ran fsck.ext4 -f on each partition, but no error was found.

Michael

6

hi there,

exactly same problem occurred on my opensuse11.3 box.
I have ran live CD and checked file system with fsck.ext4 and e2fsck, but it just said file system is clean and nothing to repair.

although something different is any messages which printed to boot screen are not in /var/log/boot.msg.
so, i tried boot again and again then could remember these error messages.

does anyone know what happening on my machine?

Moru DRS

7

Would someone with the 200 staprun error messages post output from

sudo service --status-all 
## and 
cat /var/log/messages | grep staprun  | tail -n 25
## and/or 
cat /var/log/boot.msg | tail -n 25

Also read

 man staprun

I guess each of you compiled a kernel module that failing to compile. The original post indicates a link or relocation name was too long.

8

Ermm … the staprun messages are gone after


/usr/ati/share/fglrx_uninstall

Sorry, seems to be clear now who is in charge… :slight_smile:

Michael