[Louisda16th]

I get this message that pops up suddenly everyday. After that I have to use the reset button since the computer does not shut down. It freezes during shut down. I'm using Fedora 10 x86_64 with linux kernel 2.6.27.7-134.

Quote

x7;Message from [email protected] at Dec 15 09:23:31 ...
kernel:Oops: 0000 [30] SMP

x7;Message from [email protected] at Dec 15 09:23:31 ...
kernel:Code: a0 e8 1b 5a 04 00 48 83 c4 50 5b 41 5c c9 c3 55 ba f8 ff ff ff 48 89 e5 53 48 89 f3 48 83 ec 08 48 8b 87 b8 00 00 00 48 8b 40 58 <48> 83 78 08 00 74 28 f6 47 32 04 75 0d 48 8b 77 18 48 8b 7f 10

x7;Message from [email protected] at Dec 15 09:23:31 ...
kernel:CR2: ffffff0081351248

x7;Message from [email protected] at Dec 15 09:26:07 ...
kernel:Oops: 0000 [31] SMP

x7;Message from [email protected] at Dec 15 09:26:07 ...
kernel:Code: a0 e8 1b 5a 04 00 48 83 c4 50 5b 41 5c c9 c3 55 ba f8 ff ff ff 48 89 e5 53 48 89 f3 48 83 ec 08 48 8b 87 b8 00 00 00 48 8b 40 58 <48> 83 78 08 00 74 28 f6 47 32 04 75 0d 48 8b 77 18 48 8b 7f 10

x7;Message from [email protected] at Dec 15 09:26:07 ...
kernel:CR2: ffffff0081351248

I have no idea what that means and I don't like pressing reset so many times . Is there a solution for this or will I have to wait for a kernel update?

The second issue is with k3b. Everytime I close it I get an error message from the KDE crash handler. Here's what it says:

Quote

The application unknown (k3b) crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.

When I click show detail, it shows the following:

Quote

Application: unknown (k3b), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
.
.
.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f92ce820750 (LWP 27176)]
(no debugging symbols found)
(no debugging symbols found)
.
.
.
(no debugging symbols found)
[KCrash handler]
#5 0x000000354481257d in ?? () from /lib64/libselinux.so.1
#6 0x0000003544804fef in selinux_file_context_cmp ()
from /lib64/libselinux.so.1
#7 0x0000000000000000 in ?? ()

Is there a solution for this as well?
Thanks in advance

[MorphiusFaydal]

I'll go backwards -
k3b: Looks to be an issue with SELinux. Either turn off SELinux or wait for an update.

Kernel: Try the Fedora forums. That looks like a pretty serious kernel oops, possibly related to SMP.

[Louisda16th]

Thanks for your reply

I did post a topic at the fedora forums. for the kernel problem a week back. Haven't got any reply there. . I posted in the thread again today. Hopefully some one will know whats going on. There is one more thing. Whenever I reset my PC because of this, after fedora is done loading, I get a notification that a bug report has been sent to www.kerneloops.org. I went to the link and saw that the kernel I have has a pretty large oops count.

I disabled SELinux. k3b still shows the same message after closing. Earlier I thought it was a dbus issue. A recent dbus update (1.2.6) had caused a few problems in F10. Reverting back to version 1.2.4 solved those problems. So I guess this is not due to that either.

[Jarrhed]

Try downgrading your kernel to 126 or compiling your own kernel, google how to do this, there are plenty of guides for it all around

[Louisda16th]

I stil feel its a dbus issue since a dbus update did cause quite a few problems. I did downgrade to the previous version but some problems remained. I'm guessing this is one of them.
I reinstalled fedora (and windows) yesterday. Once I'm done setting up fedora, hopefully the problem shouldn't come up again. O yeah. Ive installed mint as well.
Thanks for your replies

[Jarrhed]

Mint seems like a very nice distro but if the problem arises again, try going with the kernel 2.6.28 as, from my experience those seem to work fine

[Tom9729]

Jarrhed, on 5 Jan, 2009 - 08:34 PM, said:

Mint seems like a very nice distro but if the problem arises again, try going with the kernel 2.6.28 as, from my experience those seem to work fine

2.6.28 was released about two weeks ago...