Kernel Panic messages

yggdrasill · 2015-11-05 22:12:00

I have been having some problem with my system.
While doing some work on my computer it suddenly freeze or restarts. Caps lock sometimes goes on when it freezes.
When I restart it it freezes also when doing fsck. Again I restart and then I get kernel panic messages which I will write later.

I did memtest today and when I did multithread or what ever its called, F2, it freezes after 4 minutes, that is the minute counter
but not the plus sign in the top left corner.

journalctl -b n gave nothing I could find.

Since I think I found the problem I just wanted to ask you if I could be right.
It seems to be my new memory, Crucial 8GB. It bought it last month I think and
these messages did happen first on friday last week. I took it out and the system starts up normaly where I should have had
kernel panic when the new memory was connected.

The messages from kernel are (each line is new message for each boot):

bug unable to handle kernel null pointer dereference at 0000000000000088

Bug: unable to handle kernel paging request at 0000000081571b5b

Bug: unable to handle kernel paging request at 00000000055d4a80

Panic: double fault, error_code: 0x0

http://imgur.com/7sSA7u1.jpg

http://imgur.com/0DmGlAK.jpg

http://imgur.com/nyPwvWY.jpg

http://imgur.com/vyNc65n.jpg

EDIT: Fixed images, added more info.

Moderator edit: Converted over sized image tags to url tags https://wiki.archlinux.org/index.php/Fo … s_and_code

Last edited by yggdrasill (2015-11-06 00:45:33)

ewaller · 2015-11-05 22:29:13

Welcome to Arch Linux. Please take a look at our policies (linked above) as to pasting large images in support threads. Thanks.

Intel processor? Did you install and configure microcode uptates for your processor?

yggdrasill · 2015-11-05 22:38:59

ewaller wrote:

Welcome to Arch Linux. Please take a look at our policies (linked above) as to pasting large images in support threads. Thanks.
Intel processor? Did you install and configure microcode uptates for your processor?

Ah sorry. Yes much better to have just url rather than image.

Yes its 2.3 GHz Intel Core i3-2350M, 320GB disk, originally 4GB memory (I added 8GB to it), Qualcomm Atheros AR9285 wifi.
And no I haven't installed this microcode. So that could be my problem?

ewaller · 2015-11-05 22:41:50

Oh, yes

yggdrasill · 2015-11-05 23:09:30

Nope that didn't work. Installed the image and put it to systemd-boot conf.
Ran it, shutdown again and installed the memory. Turned it on again and the kernel panic came back.

"dmesg | grep microcode" gave:
[ 0.000000] microcode: CPU0 microcode updated early to revision 0x29, date = 2013-06-12
[ 0.104928] microcode: CPU2 microcode updated early to revision 0x29, date = 2013-06-12
[ 0.958798] microcode: CPU0 sig=0x206a7, pf=0x10, revision=0x29
[ 0.958805] microcode: CPU1 sig=0x206a7, pf=0x10, revision=0x29
[ 0.958816] microcode: CPU2 sig=0x206a7, pf=0x10, revision=0x29
[ 0.958825] microcode: CPU3 sig=0x206a7, pf=0x10, revision=0x29
[ 0.958887] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

http://i.imgur.com/WYm6o6l.jpg

ewaller · 2015-11-05 23:31:40

Invalid op code, corrupted stack, null pointer dereference. It does not seem to be the same problem every time. I was going to suggest memory, but then I noticed you are fighting with memory problems. Had I missed that, or is it part of your latest edit? You might run one of the pre-boot memory tests tests available with some of the boot loaders.

Also, you do want the Microcode updates. I see your processor does need them and the lack of those updates are the root of many subtle problems.

yggdrasill · 2015-11-05 23:38:48

Yeah you're right, the messages are not always the same. Do you mean POST test or what kind of test.
I'm using EFI, systemd-boot.

ewaller · 2015-11-06 00:02:22

Gummiboot used to have memtest86 included. I guess it went away with the movement to systemd-boot. I do see that memtest86+ is in extra, but I know little about it. There is also memtest86-efi in the AUR that looks interesting to me (I boot directly from efi using the kernel efistub) I am not at my Arch machine so I cannot play with this until later tonight (a few hours from now)

mich41 · 2015-11-06 09:45:15

yggdrasill wrote:

I did memtest today and when I did multithread or what ever its called, F2, it freezes after 4 minutes, that is the minute counter
but not the plus sign in the top left corner.
journalctl -b n gave nothing I could find.
Since I think I found the problem I just wanted to ask you if I could be right.
It seems to be my new memory, Crucial 8GB. It bought it last month I think and
these messages did happen first on friday last week. I took it out and the system starts up normaly where I should have had
kernel panic when the new memory was connected.

Well, I guess you could be right indeed. Probably either this RAM module is broken or your timings are set wrong.

yggdrasill · 2015-11-06 10:09:58

Timings you say. My two RAM modules are different from each other, the original 4GB and the new one 8GB.
Both have different timings. Does that matter?

mich41 · 2015-11-06 10:31:03

This shouldn't be a problem if you set timings to AUTO and the BIOS does its job properly, i.e. chooses timings which are slow enough for every installed module.

I'd start with setting timings, clocks, voltages, etc. to AUTO and testing each module separately. Until you get this Crucial to work alone, you can be pretty sure it won't work with other modules either.

yggdrasill · 2015-11-06 10:35:43

OK will do that if the bios allows that. Like the pictures show I'm running on HP Probook 4530s laptop so maby that feature isn't available.

yggdrasill · 2015-11-06 11:03:01

Bios doesn't allow that apparently :s

mich41 · 2015-11-06 11:09:45

I only mentioned timings because some people overclock the shit out of their systems and then act surprised when things break. If your BIOS doesn't allow OC then fine, leave it alone.

Just test these modules separately and if one of them doesn't pass memtest get rid of it.

yggdrasill · 2015-11-06 11:28:38

Uhhh I was reading about memory problems with my computer. According to the manual it supports up to 8GB.
Couldn't that be the cause of the panic and random panic messages?

yggdrasill · 2015-11-08 16:14:25

The problem seems to be a luxury problem - Too much memory
I always thought the computer wouldn't start when it has too much of it.
Oh well thank you guys for checking things out for me.

Arch Linux

#1 2015-11-05 22:12:00

Kernel Panic messages

#2 2015-11-05 22:29:13

Re: Kernel Panic messages

#3 2015-11-05 22:38:59

Re: Kernel Panic messages

#4 2015-11-05 22:41:50

Re: Kernel Panic messages

#5 2015-11-05 23:09:30

Re: Kernel Panic messages

#6 2015-11-05 23:31:40

Re: Kernel Panic messages

#7 2015-11-05 23:38:48

Re: Kernel Panic messages

#8 2015-11-06 00:02:22

Re: Kernel Panic messages

#9 2015-11-06 09:45:15

Re: Kernel Panic messages

#10 2015-11-06 10:09:58

Re: Kernel Panic messages

#11 2015-11-06 10:31:03

Re: Kernel Panic messages

#12 2015-11-06 10:35:43

Re: Kernel Panic messages

#13 2015-11-06 11:03:01

Re: Kernel Panic messages

#14 2015-11-06 11:09:45

Re: Kernel Panic messages

#15 2015-11-06 11:28:38

Re: Kernel Panic messages

#16 2015-11-08 16:14:25

Re: Kernel Panic messages

Board footer