LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   14.0 KDE-4.10.5 using config from current for kernel version 3.10.0 or 3.10.1 (http://www.linuxquestions.org/questions/slackware-14/14-0-kde-4-10-5-using-config-from-current-for-kernel-version-3-10-0-or-3-10-1-a-4175469629/)

AlleyTrotter 07-14-2013 05:59 PM

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

TobiSGD 07-16-2013 08:43 AM

The kernel mailing list is not for bug-reports, use the bug-tracker instead: https://bugzilla.kernel.org/

AlleyTrotter 07-16-2013 11:58 AM

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

slackd 07-16-2013 12:53 PM

@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
00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Ivy Bridge Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4)
00:1c.2 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 3 (rev c4)
00:1c.3 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5229 (rev 01)

Uname output:
Code:

[23:22:10] root@SamBox:~ # uname -a
Linux SamBox 3.10.1 #1 SMP PREEMPT Mon Jul 15 23:56:21 IST 2013 x86_64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz GenuineIntel GNU/Linux


TobiSGD 07-16-2013 01:33 PM

Quote:

Originally Posted by AlleyTrotter (Post 4991372)
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

I am currently testing drm-fixes-3.11 from Alex Deucher (and having some issues with that that are unrelated to your bug), which at this point basically is 3.11-rc1, but I am running that on -current, so it may be that either this is fixed already in 3.11-rc1 or it is caused by some other code in 14.0. I would recommend to give 3.11 a try or maybe setup a test installation of -current.
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.

AlleyTrotter 07-16-2013 04:14 PM

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

TobiSGD 07-16-2013 04:26 PM

Quote:

Originally Posted by AlleyTrotter (Post 4991517)
Are you using the 3.10 config from testing? Then doing 'make oldconfig' and accepting the defaults.

Exactly. After that I just change the CPU type for my Phenom II and compile it.

slackd 07-16-2013 04:37 PM

Quote:

Originally Posted by AlleyTrotter (Post 4991517)
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.

thanks
john

No. I initially used the config file from the 3.9.7 kernel. The generic one. I built 3.10 first, now i used the same 3.10 config file to bump up to the new kernel.

slackd 07-16-2013 11:06 PM

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

testing/source/config-testing-3.10.1/*: Upgraded.


AlleyTrotter 07-17-2013 09:30 AM

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
00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Ivy Bridge Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4)
00:1c.3 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 4 (rev c4)
00:1c.4 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 5 (rev c4)
00:1c.5 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 6 (rev c4)
00:1c.7 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 8 (rev c4)
00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04)
02:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
03:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57781 Gigabit Ethernet PCIe (rev 10)
04:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)
06:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller

Thanks
John

jon lee 07-18-2013 05:34 PM

I'm running 3.10 rc4.
Code:

bash-4.2$ cat /proc/version
Linux version 3.10.0-rc4-smp (root@bigbro) (gcc version 4.7.1 (GCC) ) #2 SMP Sat Jun 8 05:48:22 EDT 2013

Notice it says 2. The first one panicked early in the boot process. Dunno which config it was, but I was definitely more conservative the second time around.

If you want I can pastebin the config that worked for me.

AlleyTrotter 07-19-2013 12:14 PM

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 07-19-2013 01:55 PM

No prob.
http://pastebin.com/8GRcisxq

kmesg
http://pastebin.com/V0KaaYpL

AlleyTrotter 07-19-2013 09:03 PM

jon_lee
Thanks for your config file but I am working with a 64 bit kernel not 32.
John

AlleyTrotter 07-23-2013 08:18 AM

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:49 PM.