14.0 KDE-4.10.5 using config from current for kernel version 3.10.0 or 3.10.1
Anyone care to comment. This kernel bug appears when using the title software on a panther point Z77 chipset and Intel core I5 3570K with on processor graphics and 32GB memory. Happened while web surfing with FF17 or FF22. UEFI boot GPT partitions
Wondering if I should send to the kernel mailing list Thanks John second thumbnail note that the second line IP (instruction pointer?) has an identical address for both dumps |
The kernel mailing list is not for bug-reports, use the bug-tracker instead: https://bugzilla.kernel.org/
|
Thanks TobiSGD.
I was hoping to not be the only one trying out 3.10. Apparently no one else is using 3.10 or the bug (as stated in the dump) is unique to my setup. I'll give it another day or two and then try to learn the 'proper' way to submit a suspected bug to Linus. john |
@AlleyTrotter
I am using 3.10.1 on my laptop. Just compiled it yesterday. It boots up fine and works well. Here is an lspci dump from my laptop. I am guessing it's a problem unique to your configuration. It might also be a config problem. Code:
[19:20:54] root@SamBox:~ # lspci Code:
[23:22:10] root@SamBox:~ # uname -a |
Quote:
I actually never really tested 3.10, I have compiled it to test UVD support for my videocard, but wasn't able to figure out how to make a package of the upcoming Mesa 9.2, which is needed for that. |
slackd are you using the config file from Slackware-current/testing? 3.10 takes several hours to fail for me possibly as many as eight. I might also add that both huge and generic fail with the same message.
TobiSGD I think I may give 3.11 a try. It will probably be much easier than getting on the bug-list. Are you using the 3.10 config from testing? Then doing 'make oldconfig' and accepting the defaults. thanks john |
Quote:
|
Quote:
|
Try now, it should work!! :P
From: http://www.slackware.com/changelog/c...php?cpu=x86_64 Code:
Tue Jul 16 21:18:56 UTC 2013 |
I just did a diff on the old /testing/config-generic-3.10.x64 and the new /testing/config-generic-3.10.x64, the only difference in them is line 3 which names the kernel version. So no help yet from the home planet.
I am trying a rebuilt of 3.10.1 starting with my working 3.9.10 config while accepting all the defaults when make oldconfig. Ran all night with just a terminal open dumping files to standard out without problems. That is what I suspected because the kernel dump mentions drm. I am now running for about two hours in Kde without a failure, if it lasts all day I will try to find the diff in the two configs. If of interest here is my lspci Code:
/sbin/lspci John |
I'm running 3.10 rc4.
Code:
bash-4.2$ cat /proc/version If you want I can pastebin the config that worked for me. |
So far so good
I've been using my working 3.9.10 + accept all defaults configuration to build my 3.10.1 kernel for more than 24 hours successfully. If I get another 24 hours of no bug I will begin to apply the differences in the testing config to my configuration to try and isolate the culprit. Diff tells me there are 126 differences between the two files, so this may take a while. Since the bug dump mentions page swap and also drm I will probably start there.
Thanks to All john OOPS spoke too soon crashed about 5 minutes ago jon_lee I would appreciate a look at the .config you are using thanks john |
|
jon_lee
Thanks for your config file but I am working with a 64 bit kernel not 32. John |
3.10.2 No Help
Using generic config from testing on 3.10.2 kernel still crashes. Only added ext4 support to generic. It seems to crash only after a resume from kde "suspend to ram". Takes about 1 hour of usage after resume to crash.
I have a new photo but it refuses to upload Some additional info The kernel generic-3.10.2 also crashes on a fresh install of current. I built the generic kernel after installing current with only ext4 set to Y. Again it crashed after resume from "suspend to ram" in almost to the minute one hour after a resume. |
All times are GMT -5. The time now is 07:48 PM. |